Actions
Processes module1. General
The actions are available in the Elements area; they will be described here. Actions can be connected to conditions and other actions. The following process elements can only be configured if a triggering data group (e.g. via a data group event handler) is defined in the process chain:
- Data group action
- Timer action
- Filter condition
2. Data group action
With a data group action, data records can be inserted or existing data records can be edited or deleted. Data group actions can only be configured if they are connected to a fully configured data group event handler.3. Email action
With this action, notifications can be sent via email when specific events occur. In order to use this function, the Email service must be configured in the Tools module. To send emails with links to portal pages via the process, the base URL in the portal properties must contain the root URL of the portal (such as https://portal.example.com/).4. WebSocket action
A WebSocket actions makes it easy for you to write WebSocket messages and connect them to a topic.More information about WebSockets is available here: Please note: You can also use Groovy actions to write WebSocket messages and connect them to a topic. More information about this is available in the chapter Groovy action with WebSocket functions.
5. Push notification action
With this action, notifications can be sent to the Intrexx Mobile App. You can define the sender, recipients, content and link destination of the action in the properties dialog.6. Document action
This action allows you to perform event-controlled document generation. The document can be saved directly to a data record. The following requirements must be met before you can use this action:- The desired view page must be activated for document generation.
- A template must be created that contains formatting information for the text.
- A file data field where the documents are stored is required.
7. Data group timer action
With a data group timer action, you will define a time-controlled event, like you do with a Global timer that will be run in the course of the process. As opposed to the global timer, a task will be generated once the timer action is initiated in the process chain. The data group timer action must be connected to a data group or Timer event handler or that reacts to an additional timer action or a global timer related to a data group. When it is triggered, it generates a task for every received data record. In the Tools module, the data record GUID will be listed alongside each of these tasks. This GUID can then be used in Groovy or generic event handlers.Example:
A data group event handler reacts to a change in reports. The timer should report each unreleased report via email. If you want to react to the data group timer action that you have defined you will require an event handler (timer, Groovy, or generic events handler), which will react to the task that is created via the data group timer action at the defined point in time.