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

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

Default service request/response structure

When calling services, it is possible to choose from a predefined list of call types: XML_HTTP JSON_GET JSON_POST   These are the default request and response structure for the above call types: XML_HTTP Request: XML_HTTP Response: JSON request and response:

Hello, World!

This example demonstrates how to create a simple ‘Hello, world!’ application, test it in the PROCE55 Modeler and deploy to a mobile device. To do this, you need the following: PROCE55 Modeler installed on a Windows PC (download here) a mobile device running Android, iOS or Windows 10 Mobile with the PROCE55 Runtime Environment installed […]

Screen UI Elements

Every visual element you put into your app’s screens is assigned a system name composed of the screen name, element type and a number (ranging from 1 to n). For example, the first text input on a screen s1 is named s1_i1. If you add another text input to that screen, it would be s1_i2… […]

How the platform works

The PROCE55 Mobile platform allows developers to create apps using the PROCE55 Modeler (for Windows) and execute the apps in the PROCE55 Mobile RTE (Run Time Environment) for Android, iOS and Windows 10 Mobile. Deployment of PROCE55 apps can be done directly from the Modeler using various methods (PROCE55 cloud, custom app repositories or custom […]

System actions

System actions can modify user interface element properties and perform various simple tasks such as scanning bar codes, showing messages or adding rows to tables. System actions usually have at least one parameter (e.g. a name of the screen element to be modified). This is the current list of all system actions: Exit Exit the […]

Conditions and Condition Blocks

Conditions can be inserted into action flows in order to stop the execution if a condition is not met (raising a warning dialog), or to exclude parts of the sequence from executing based on condition expression. The expression can be a complex string to be passed to the JavaScript eval() function. When writing condition expressions, […]

Skip to toolbar