Automatize
Migrations · 02 · Terminal → Web
← All migrations

Replacing the terminal UI

From green screens and function keys to a web UI new colleagues pick up quickly.

Same work, fewer screens.

Terminal screens are fast for those who have known them for twenty years, and a wall for everyone else. We map every screen, field and function key and build a web UI around the task instead of around the transaction code. The shortcuts stay, the emulator goes.

Start the conversation →See the diagram →

The same record, before and after

Illustration
Fictional example. On the left a customer record on a terminal screen, on the right the same record in the web UI: named fields, the status in words and actions as buttons instead of function keys.

What you can expect

01
Designed per task
What takes four screens and three transaction codes today becomes one page.
02
Fast on the keyboard
Experienced users keep their pace: shortcuts, logical tab order, no mouse needed.
03
No emulator
The UI runs in the browser, with roles and permissions per screen. Nothing to install on the workstation.

How we do it

01From screen to page
Screen inventory
Every map, field and function key documented, with the validations behind it.
Flows merged
Screens that always follow each other become one page with the steps visible.
02For the user
Search and filter
Find a customer by name, number or town, without knowing codes by heart.
Validation while typing
Errors appear at the field, not as a code at the bottom of the screen.
03Roll-out
Per department
Each department switches when its screens are ready and tested.
With the users
The people who use the system every day test the screens before they go live.
■Browser-based · no client install
■Fully keyboard operable
■Roles and permissions per screen
■Multilingual: NL · FR · EN

Curious what is inside your COBOL?

We start with an inventory.Start the conversation →