Multiple UI elements can be linked to a specific action via a UI action. If the action is just a method to interact with the process, the UI Action adds information about how that UI should react. For example, should a loader appear after executing the action, should a modal be dismissed, or if some default data should be sent back to the process.
UI actions create a link between an action and a UI component or custom component.
The UI action informs the UI element to execute the given action when triggered. Other options are available for configuration when setting an action to a UI component and are detailed below.
There are two main types of UI Actions:
This is a UI action that describes how a UI Component (generated or custom) should interact with a process Manual action.
First, we need to configure the manual action that will be referred from the UI Action. For more information on how to add an action to a node, and how to configure it, check the following section:
application.client.email
; if we need a button that will send back all the form elements that have keys that start with application.client
we can add just this partapplication.client.email
, application.client.phone
, application.client.address
and we send application.client.age
this key will not be persistedWhen this prerequisite is ready we can define the UI Action.
UI Actions and Actions must be configured on the same node.
Multiple configurations are available - ACTION type example:
You can add an event depending on the element that you select. There are two events types available: CLICK and CHANGE.
Not available for UI actions on Custom components.
The action type dropdown will be pre-filled with the following UI action types:
Used to create an action that will open a link in a new tab.
If we toggle the EXTERNAL type, a few new options are available:
For more information on how to add actions and how to configure a UI, check the following section: