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:
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.
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/).
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.
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.
Click here for general information about parameters.
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 that reacts to an additional timer action or a global timer that is connected 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.
A universal timer action will be implemented when a task should be created in the process chain. In contrast to a data group timer action it will not react to data records but rather a task will be generated once, when the timer action is triggered during the process. Here you have the choice between setting a relative or absolute timer.
A web service request can be performed with this action.
To be able to structure Intrexx applications even more flexibly, you have the ability to integrate Groovy scripts into your processes. Groovy is considered to be better integrated than most other script languages on the Java Virtual Machine. Existing libraries or Groovy objects and classes in Java can be used easily. From the properties dialog you can reach the script editor where you can compose scripts and add them to the process.
The generic action uses events from the functions in Intrexx classes, or third-party classes.
With this action you will define a specific user whose context should be used to perform the subsequent steps of the process. This makes it possible to use the permissions of a user in the process to make changes in an Intrexx portal or in released mailboxes in Microsoft Exchange.
With this element, you can integrate one or more existing processes, which respond to the same data group event, into the current process. You can also specify the order that the processes should be executed in. The event, which triggered the invoking process will then be transferred. In the invoked process, the event may not be identified based on its class but rather via its interface (e.g. in Groovy event handlers). This rule always applies. The property g_wfContext.internalTrigger, available in Groovy, is set to true in the invoked process. The processing takes place synchronously, in the same thread and in the same transaction. Exceptions, which occur in the invoked processes, will be transferred to the invoking process.
With this element, the process will be stopped at exactly the location where the element has been placed in the chain.