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.

Step 1

At first, the Event Button Press on the Login Mask is assigned to the Login Activity.

Step 2

If the Login will be successful, we want to display the Username (filled automatically by using an Autofield) in the right upper corner on the Application. To fulfil the requirements, we map the autofield in the ui action with a text widget.

Step 3

If the Login was not successful, we change the Login Mask to Error via another UI Action

The Server Action enables you to configure the following actions:

• Login: perform a user login inside an application
• Logout: perform a user logout inside an application
• Template: address a template
• E-Mail: send an e-mail

After mapping the according parameters you can decide which port you’d like to connect.

User Credentials

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:

Single Sign-on

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:

OAuth 2.0

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:

1. Service describes the OAuth service provider (e.g. Google, Amazon, Azure…) that expects a string that represents the name of a provider configured in the server settings.
2. UserSync expects a Boolean value to switch between the following two possibilities:
   1. 1. Login via OAuth by synching a user profile (true)
         This will synchronize the retrieved information with a Simplifier user (if there is one for the credentials) or create a new user. In both cases, the current login is overwritten and all permissions are revoked.
      2. Login via OAuth by adding the OAuth token only to the Simplifier token of the current user or app (false)
         This does not synchronize the user, but adds the received token to the current user or app profile (if the app is configured to allow anonymous users), retaining all previous logins and associated permissions.

SAML 2.0

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:

1. Service – must be an existing SAML authentication setting.
2. UserSync – should be true if a successful login replaces the primary user login.

The behavior is analogous to the OAuth login.

Logout

For the Server Action Logout you don’t have to configure anything additionally.

Template

Use Templates to generate dynamic text, for example, as content for an email. Instructions on how to create a Template are given in this article.

The Server Action ‘Template’ has the parameters:

• Template: select the template that you want to use
• Show Busy Indicator: if set to true, a busy indicator will be shown on screen during the template-based text is generated

After selecting the template that you want to use, set the respective input parameters that are required for the selected template.
The output parameter ‘Template’ contains the template-based text (the text that is defined inside the template, with the dynamic parts being replaced by the values from the input parameters. You can use this text for any given use case, for example, setting it as the content for an email.

E-Mail

For the Server Action ‘E-Mail’, you can define the following parameters:

• Receiver (mandatory): The e-mail address of the person(s) that should receive the mail
• CC: The e-mail address of the person(s) that should also receive the mail
• BCC: The e-mail address of the person(s) that should also receive the mail, but is/are not shown in the recipient list
• Sender: The e-mail address that is shown as the sender of the mail
• Subject: The text that is displayed as the subject of the mail
• Body: The text that is displayed as the content of the mail (for example, text generated by the Template Server Action)
• Show Busy Indicator: if set to true, a busy indicator will be shown on screen during the template-based text is generated

For the parameters Receiver, CC and BCC, you can also specify multiple e-mail addresses. To do so, the e-mail addresses have to be separated by semicolons.

There are no specific output parameters for the E-Mail Server Action. Use the green success node or the red error node of the shape to control the process after sending the mail.