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:     […]

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 […]

To press button (and activate the underlying action sequence) when a text input contains a specific text, put the following code to your app’s JavaScript window. Modify your screen and variable names accordingly.

Put the following code to the app’s JavaScript window, to add input focus to a text field element every time a specific screen is shown:

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 […]

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 […]