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
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
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 timerrelated 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.
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.
8. 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.
9. Web service action
A web service request can be performed with this action.
10. Groovy script 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
where you can compose scripts and add them to the process.
11. Generic action
The generic action uses events from the functions in Intrexx classes,
or third-party classes.
12. 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.
13. Include processes
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.
14. Stop process
With this element, the process will be stopped at exactly the location
where the element has been placed in the chain.