Processes module

Actions can be connected to conditions and / or actions. The following process elements can only be configured if a data group is defined in the process chain to be run:

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.

Email action

With this action, notifications can be sent via email when specific events occur. In order to use this function, the E-Mail-Service must be set up in the Intrexx tools. In order to send emails with links to portal pages via the process, the Base-URL field must be filled in the portal properties with the root URL of the portal (such as http://myportal/). You can reach the portal properties from the Portals module via the menu item Portal / Portal properties. Add an Email Action, and open the properties dialog by double-clicking on the element.

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: General information regarding this topic can be found here.

Data group timer action

With a data group timer action, you will define atime-controlled event that will be run in the course of the process. The general properties of the data group timer action correspond to the general properties of the global timer. As opposed to the global timer, for a data group timer action a task will only be generated once the timer action is initiated in the process chain. This task will be listed and described in the Tools module. The data group timer action must be connected with a data groups or timer event handler, which reacts to an additional timer action or a global timer with a relation to data groups. When it is initiated, it will generate one task per data record delivered. In the Tools module, the data record GUID will be carried along with each of these tasks. This GUID can be further used in Groovy or generic event handlers.


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.

Universal timer action

A universal timer action will be implemented when, in the chain of a process, a task should be created. In contrast to a data group timer action it will not react to data records here; rather, a task will be generated once, when the timer action without DG is executed in the handling of the process. Here you have the choice between setting a relative or absolute timer.

Web service action

A web service request can be executed after a condition.

Groovy script action

In order to be able to structure Intrexx applications even more flexibly, you have here the ability to integrate Groovy script into your processes. Groovy is better integrated than most other script languages into the JVM. Existing libraries or Groovy objects and classes in Java can be used easily. From the properties dialog you can reach the script editor, in which you can compose scripts and include them in the process.

Generic action

The generic action uses events from the functions in Intrexx classes, or third-party classes.

User switch action

With this action you will define a specific user, in whose context the following steps of the process will be executed. This makes it possible to use the permissions of a user in the process for modifications in an Intrexx portal or in released mailboxes.

Include processes

With this element, you can include one or more existing processes that respond to the same data group event in the current process flow. Thereby you can also specify the order in which the processes are to be executed. 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.

Stop process

With this element, the process will be stopped at exactly the location in which the element has been placed in the chain.