Each app is contained in a single file which can be transported to a mobile device. The file can be modified using the PROCE55 Modeler and published using cloud or custom repositories in local networks or Internet servers. Each app file contains everything the app needs – the application model (its screen UI definitions and […]
It is possible to display the detailed log view on mobile devices by scanning the ‘Enable Debug Log’ configuration QR code, which you can generate using the modeler’s Support menu. This will temporarily activate the logging (until the mobile client application is restarted). Now you can enter your app, carry out the necessary task and view […]
Aside from ordinary screen elements, which can be referred to using their system names (s1_i1, s2_p3, …) you can create your own custom variables. Such custom variable names must start with one of the following: C_ CUS_ CUST_ CUSTOM_ For example: C_IPADDRESS1 C_SERVERNAME C_VAR1 CUST_VAR2 Creating such a variable is simple, just transfer a value […]
Simply transfer an empty value to the image element, e.g. s1_p1 or use the ‘ClearGallery’ system action with your image element name as a parameter name (e.g. s1_p1).
Every PROCE55 app consists of several screens. By default there are minimum of two screens: ‘initial’ and ‘s1’. The initial screen is where the app starts processing. It contains a single button marked as ‘[x] Auto-click’, which means it is ‘clicked’ automatically by the engine, taking the screen navigation to the button’s target screen (‘s1’ […]