The main process element is the execution of actions. Simply drag & drop any number of actions to connect in a series, building your ideal process.
The actions are available in the "Elements" area; they will be described below. 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
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.
As always, email is the leading notification medium for dynamic processes. Use this action to send content to selected recipients at will. Likewise, the recipient can be added just as dynamically as email content – from individual pages from Intrexx Portlets (Optional), to pages created with Groovy or Velocity, through to text-only mails – every email-related need can be implemented here.
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 field "base URL" in the portal properties must contain the root URL of the portal (such as https://portal.example.com/).
Using WebSockets enables dynamic updating of content displayed in the browser. No user action is required for the process to send messages to the user or refresh content in the browser. Sending the messages or refreshing the browser content is automatically triggered by this event. This can be used, for example, to signal incoming messages, indicate problems in a production line, change views of data in real time, and enable another dimension of user interaction.
More information about WebSockets is available here:
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.
Push notification action
This action lets you send users a push notification. All you need is the Intrexx Mobile App. You can define the sender, recipients, content and link destination of the action in the properties dialog.
Templates can be created on the basis of application pages created with Intrexx, which can be designed as desired with LibreOffice, for example. These documents are then appropriately enriched with the data of a specific data record and made available as a PDF or also as an Office document directly in the process. The document engine with its template function is a very powerful tool and allows transparent creation of high-quality reports with the dynamic data from Intrexx low-code applications, which is ideal for generating certificates, document templates, offers, and much more.
The document action enables event-driven 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.
General information on the topic of "Creating documents" can be found here.
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. Here is an 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.
Universal timer action
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.
Web service action
A web service request can be performed with this action.
Groovy Script Action
Groovy is a scripting language similar to Java and is considered to be better integrated than most other scripting languages on the JVM. Everything that can be implemented in Java can also be implemented in Groovy. This is the most powerful process action in Intrexx – but it also departs from the no-code area and requires a certain know-how. With the necessary know-how, however, any conceivable application scenarios that can be implemented with software can be realized. You can integrate any libraries and directly query databases via SQL and thus have complete freedom in implementing your requirements.
Groovy script can be integrated into processes easily. The properties dialog of the Groovy action can be used to access the script editor where you can write the desired script. It is then executed at the exact point where the action is located in the process chain.
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 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.