The Navigation element is used to trigger a navigation from one screen to another. By dragging it to the main screen, a list of screens to navigate to will appear in the right pane.
You can set that the navigation should navigate back, or choose between several transitions: Slide, Fade, Flip or None.
In most cases, a navigation will be used when clicking on a button, so by combining a clickable event (e.g. button press) with a navigation element this can easily be achieved.
With the UI Action element, you can map different widgets, variables and auto fields to another.
Let’s say there is a very simple login screen with an input field for the name and a button to submit.
The button should not be responsive, as long as the login field is empty. This can be achieved with the UI Action in the Process Designer.
At first, assign the input field “InputUsername” to the Event.
Next, a condition is needed. Check, if the value of the input field equals an empty string.
If the condition is true and there is nothing written in the input field, the button should not be responsive.
Add a UI Action and set within the mapping dialog the constant (boolean, false) on the left side (source) and map it to the equivalent widget on the right side (target). Select the screen, widget and property (in this case “enabled”).
|For the other scenario, when there actually is an input written, you can connect the condition to a second UI Action and set the boolean via the constant on true.|
|In this example, we have an application that writes the value of the first widget to the second input field and writes the value of the auto field (username) to the third widget after clicking on the corresponding buttons.|
Now in the Process Designer, use 2 Events and 2 UI Actions for this.
We’ve already added the press event on the first button and now we have to add the UI Action. By clicking on the mapping dialog, you can open the mapping.
Connect the value of the widget Input1 with the widget Input2. Select the property that we’d like to connect by double-clicking on the widget.
|To connect the auto field with the third input field, add the auto field and select the one you need, also by double-clicking on it.|
|This is the result of the mapping:|
The Mobile Action element enables you to use mobile features within the application.
Drag and drop the activity ‘Mobile Action’ underneath ‘Action’ into the drawing area.
Currently, there are 14 different actions implemented in the Simplifier. Use the input/output mapping to define the source for the input (request) and the destination for its output (response).
|Determine how many pictures should be taken.|
|Set the format of the code you want to scan, the orientation of the camera and write a text in the prompt property.|
|Define how many milliseconds the mobile device should vibrate.|
|Meter appearance||String||See the table below|
|Number of counters||Integer||1, 2 (from dropdown)|
|Integer digits||Integer/String||AUTO, 1-n|
|Fraction digits||Integer/String||AUTO, 1-n|
|mechanical_black||White text on black rollers|
|mechanical_white||Black text on white rollers|
|lcd_edl21||EDL21 and similar meters with LCD 7 (three-digit OBIS code to the left)|
For the output mapping you can use the following parameter:
|image||string||Image of the scanning process as data url|
|line1||string||Result of scanning the first counter (always set)|
|line2||string||Result of scanning the second counter (only set if 2 counters were scanned)|
|line1ObisCode||string||Result of scanning the first counter’s OBIS code (only set if meter appearance was set to lcd_edl21)|
|line2ObisCode||string||Result of scanning the second counter’s OBIS code (only set meter appearance was set to lcd_edl21 and 2 counters were scanned)|
|This is a native feature for talking with a user via audio- or video live streaming. The user can be statically configured. Furthermore, you can set a fullscreen.|
|By providing the mobile action a path to a video, it will play the video in a full-screen mode.|
|The mobile action Play Audio just needs an audio file path.|
|This mobile action will trigger a native notification.|
|So the Notification will be displayed on your mobile device.|
Text to Speech
|The mobile action GPS need to be initialized at first. It’s recommended to do this in a screen onInit function.|
|When it’s initialized, you can access the longitude and latitude by the Auto Field type Geolocation. For that, you need to open the mapping dialog of the UI Action. Then you can drag the auto field in the middle and by double clicking on it you can select the longitude/latitude/. Then connect it with the appropriate widget.|
|This mobile action will show a native toast, with a constant or by using the input mapping. You can specify the duration how long the toast should be displayed (Short or Long) and the position (Top, Center or Bottom).|
|You can set and lock the screen orientation of the mobile device. Possible values are Landscape, Portrait, Landscape (Primary), Landscape (Secondary), Portrait (Primary), Portrait (Secondary) and Unlock.|
|The current screen orientation can be accessed by a new characteristic of the Device Auto Field.|
|With this mobile action, your mobile device can toggle light.|
|The Server Action enables you to configure the login or logout for an application, address a template or send an e-mail.|
After mapping the according parameters you can decide which port you’d like to connect.
|success||The process will be executed after a successful login or logout.|
|error||The process will be executed after a failed login or logout.|
|already logged in||The process will be executed if the user is already logged in.|
The Server Action needs two parameters as input if you want the user of the application to fill in his username and password.
You can map the widgets in which the user fills in the information with the equivalent input parameter. (By double clicking on the widget, you can choose the exact property that you need).
|The Login screen of your application might look like this:|
You can use a Single Sign-on if you want to allow a user to use a single set of login credentials to access multiple applications. In difference to the first login method, you have to map an additional parameter, the authentication.
Therefore you have to add this authentication method to the Simplifier in advance (this will be an admin task – take a look at “Settings for Admins“).
The name that was given to the authentication is the one that is needed as an input parameter.
|This is what the input mapping should look like:|
|The login screen of your application might look like this:|
|Select OAuth as login in the server action and open the mapping dialog.|
|Within the mapping dialog you have the opportunity to choose between two parameters:|
It is possible to log into a business app via SAML 2.0.
Within the mapping dialog, you have the opportunity to choose between two parameters:
The behavior is analogous to the OAuth login.
|For the Server Action Logout you don’t have to configure anything additionally.|
|Use the Server Action Template to address templates.|
With the help of parameters, it is possible to pass data to the template.
Don’t forget to map the input and output. The complete template will be returned as a string.
The Server Action can be configured to send e-mails.
Enter the sender and receiver e-mail, optionally CC and Bcc. You can enter multiple e-mail addresses for the receiver, CC and Bcc – in this case, the e-mail addresses have to be separated with a semicolon. At least, enter the subject and the body in HTML. For better user experience, it is possible to maximize the editor.
It is also possible to use the mapping dialog to this instead of using the settings panel.
Important: If a mapping is set, the settings in the panel are not considered.