Deleting table rows

Removing rows from a table on a mobile app screen can be done in several ways: 1. Using a system function “TableDelRow” – removes the currently selected table row 2. Using a JavaScript function you can loop table rows and make changes to row data: var table1 = PROCE55_GetElementByName(‘s1_t1’); for (var n = 0; n […]

How to address table element values

The screen table elements (named e.g. s1_t1 = screen 1, table 1) can hold a list of values organized in columns (similar to a spread sheet or a database table). You can populate the table manually (by defining its values at design time using the modeler), by JavaScript functions or a web service response (or […]

What exactly is packaged with every app

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

Enabling the debug log on mobile devices

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

Creating custom variables

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

Screen navigation

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

Skip to toolbar