Screen by screen development
Every screen needs to be modified individually using custom scripts. Every device type requires screen by screen development effort.
Long projects. High costs
What starts as a UI improvement project can quickly become a large development exercise.
WiFi drops. Work stops
Lose connection and session date is lost, with users forced to log back in each time.
Changes require development
If updates are made within ITS Mobile, new HTML templates are generations and any previous modifications can be lost. Back to rework, more testing, more effort.
Fixed screen profiles
Screens are fixed sizes and need setting up for each device type. Users are not able to utilise native device features such as cameras or gesture control.
Not futureproof
Any screen modifications you make aren’t guaranteed to work with future SAP updates and releases. When SAP changes, you may need to configure your UI from scratch.
Clear screens
Remove unwanted fields, rename labels, change font colour and sizes. Screens that only show what you need to know.
.jpg)
Built for work
If WiFi drops, PreBilt maintains session data and users simply pick up where they left off then the connected is restored.
Less to remember
Clear descriptions for menus, functions and exception codes makes the experience simpler for users.
Device agnostic
Screens automatically render to the size of the device being used, enabling a hybrid device landscape that provides the right device for the right process.
Changes with configuration
Functional resources can quickly make changes to screens in seconds, removing reliance on IT and technical resource.
Built to flex
Add functionality to meet changing business needs instead of being restricted to core transactions.
