Checking the network availability before making service calls

Mobile users often work at places with low or missing network connectivity. To avoid problems when calling back-end services, you can put conditions into your action sequences to make sure that mobile devices have the necessary network connectivity. In order to do this, the PROCE55 Mobile run-time environment offers the following system variables:     […]

Reading NFC tag values

When a user approaches an NFC tag using their mobile device, the mobile operating system reads its contents and tries to find the best way of processing it. When running, the PROCE55 Mobile run-time environment takes the NFC tag value from the operating system and is ready to use it. You can easily put the […]

Applying additional post-processing and styles to a screen after rendering

There are two JavaScript functions triggered after each screen is rendered. If either of them is present in your application, it is called automatically by the run-time environment, allowing you to apply additional changes to the screen being displayed: onTableShown(TableName) – called once a table has been fully displayed onScreenShown(CurrentScreen) – called once the whole […]

RTE Upgrade

If you have installed the mobile Run Time Environment (PROCE55 RTE) from a mobile app store, whenever there is a new version of the RTE, you can do the update. All the installed PROCE55 apps remain installed and will work with the newer version of the RTE. If you remove (uninstall) the PROCE55 RTE from […]

System variables

This is a list of system variables that can be used in PROCE55 apps: User profile data: SYS_USER_NAME_FIRST SYS_USER_NAME_LAST SYS_USER_PERSON_ID SYS_USER_ORGANIZATION SYS_USER_PHONE SYS_USER_EMAIL Authentication: SYS_USER_LOGIN SYS_USER_PASSWORD Transaction control: SYS_TID (transaction ID of the currently processed flow’s action) SYS_COUNTER (system counter variable which can be incremented by the ‘Increment’ system action) SYS_RESULT (the decision variable controlling […]

Using variables

Every user interface (UI) element (text label, text input, button, etc.) is automatically assigned a variable name, so that it is possible to modify the element properties and use its value in various system actions. For example, the first text input on the screen s1 would be named as s1_i1 (= sreen 1, input 1), […]

Skip to toolbar