Page History
Overview
The picture below gives an example of an adhoc action node in the process editor. In this case "SendReminderToCustomer" is an adhoc task that is required, has a precondition and can be performed more than once.
The table below explains the meaning of the icons within the node:
| Icon | Description |
|---|---|
| Represents a process task |
| Represents whether the node is ad hoc |
| The ad hoc task's precondition is either FALSE or Conditional |
| The ad hoc task requiredness is either TRUE or Conditional |
| The ad hoc task is repeatable |
Adhoc task
Is a process task which is used outside a sequential process. The availability of these tasks are based on pre conditions.
...
| UI Text Box | ||
|---|---|---|
| ||
At runtime, it is possible to trace task actions: Process Traceability. |
Adhoc process
It is possible to include an adhoc sub-process in a process. This sub-process acts as a collection of process components, so a sub-process will be used to organize process drawing more clearly.
...
| UI Text Box | ||
|---|---|---|
| ||
When the pre-condition of an adhoc process becomes FALSE, the process and all its contents will be cleared before process flowing is evaluated. This will cause tasks that would lead to an exit node to not trigger that exit node. |
Adhoc Message event
An adhoc message event functions as a start message within the context of a process/case. The adhoc message event node can be connected to these nodes: Task, Process, Split, conditional event, Message event, Timer event using a connector.
...
Name: Autogenerated ID for the node. It can be edited but must be unique within the process module to function.
Message Event: Using a dropdown the name of one of the available Message Events can be selected. This way the message event is connected to this node and will respond as modeled when this message event is received by the process engine. The corresponding fields which are available for the selected message event will appear on the screen.
Catching condition: A condition which can be inserted to assure that only the message node for which the condition is TRUE. The catching condition is modeled by selecting the name of one of the datafields available in the message. The condition will become TRUE if the value in the message equals the value in the profile of the case.
Field name: A list of names of the datafields which are available in the message. These name are modeled at the Message event.
Target attribute: The entity and attribute can be selected in which the data which is carried with the message event will be inserted in the profile. The process engine will retain this data in the process engine database.
Datatype: Information on type of data received in the message
Multivalued: Indicates if the data in the field can be multivalued.
Required: Indicates if the a value is required at filling the message. This field must be mapped to a target attribute.
Adhoc Conditional event
An adhoc conditional event functions as a start within the context of a process/case. The adhoc conditional event node can be connected to these nodes: Task, Process, Split, conditional event, Message event, Timer event using a connector.
...
Name: Autogenerated ID for the node. It can be edited but must be unique within the process module to function.
Condition: A condition which has to evaluate to a boolean value. If the Value is TRUE the event is caught and it will start flowing from that point. The profile of the process/case will be used for the evaluation. The node will be evaluated at each change of the profile of the process/case.
Adhoc Timer Event
An adhoc timer event functions as a start within the context of a process/case. The adhoc timer event node can be connected to these nodes: Task, Process, Split, conditional event, Message event, Timer event using a connector.
...
Overview
Content Tools