- Created by Annegret Bernhardt, last modified on Feb 01, 2021
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 6 Next »
The following BPMN elements are supported for modeling in the Designer:
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
Page | Description | Execution | Particularity |
---|---|---|---|
Image (BPMN) |
The Image element enables the user to display a picture on the canvas, for example for documentation purposes. |
None. The content of this element is ignored during execution. |
Use the attribute Image in the Attributes Panel to upload a picture into the empty frame or insert a link to an existing picture:
|
Start Event |
Use a Start Event to start a BPMN model. |
Name |
A start event can only be created via the elements toolbar. |
Timer Event |
Timer Events are triggered by a defined timer. You can use the timer event in the Designer as an intermediate event or as a boundary event:
Plain Event, Message Event and Timer Event can be used as boundary events along with User Task and Receive Task. When using the events as boundary events, attach the element directly to the border of the corresponding task:
To set the duration of the timer, the event should be trigged by a persisted property of type integer or datetime. You have two options to set the timeout in the attributes panel:
|
On Event: Without input or output parameters. |
To set the duration of the timer, the event should be triggered by a persisted property of type Integer or DateTime.
In the Attributes Panel, select the persisted property you want to use. If the drop-down list of attribute Timeout is empty, you need to create a new persisted property of type Integer or DateTime first. Depending on the type of the property, you have different options to set the timeout:
The value of the timeout can be specified at development time (default) or at runtime. |
Timer Start Event |
A Timer Start Event allows you to start a BPMN model after a defined cycle or at a defined time. Every time the timer is triggered, the model will be started. |
On Event: Without input or output parameters. |
A start event can only be created via the elements toolbar. Another particularity of the Timer Start Event is the attribute Timer which is available in the Attributes Panel:
To define the timer settings, click to open the timer editor. For detailed explanations see How to Use the Scheduler/Timer. |
User Task |
A User Task waits for an external trigger to arrive which is released by human action, for example after a form has been filled. If the process execution reaches a user task, the process stays in a wait state until a specific message is received by the engine, which triggers continuation of the process. |
Name |
|
Service Task |
A Service Task is executed automatically when the process reaches it and the process continues to the next element when the execution ends. Use the execution pane to create the corresponding execution diagram defining the service task. |
Name | - |
Relation |
The relation connects two objects. The direction of the arrow marks the process flow. Most relations are of regular type with the exception of outgoing flows of Exclusive Gateways.
|
Only on regular outgoing sequence flows of exclusive gateways:
|
- |
Receive Task |
A Receive Task waits for an external trigger to arrive which is released by an external system. If the process execution reaches a receive task, the process stays in a wait state until a specific message is received by the engine, which triggers continuation of the process. |
Name | - |
Plain Event |
The plain Event is able to catch signals. You can use the event in the Designer as an intermediate event or as a boundary event:
Plain Event, Message Event and Timer Event can be used as boundary events along with User Task and Receive Task. When using the events as boundary events, attach the element directly to the border of the corresponding task:
|
On Exit: Without input or output parameters. |
Trigger Events: Use the attribute Trigger Events in the Attributes Panel to define which button of a form associated to the element triggers the default process flow of a BPMN process. This attribute is only available for boundary events. |
Parallel Gateway |
Use the Parallel Gateway to model concurrency in a process. You can use the object to fork the process. The functionality of the object is based on the incoming and outgoing process flows.
|
None. | - |
Message Start Event |
With a Message Start Event you can start a BPMN model. "Message" is not restricted to emails or calls: Every action that represents or contains information for a recipient is a message. |
On Event: Input message (define the corresponding type of message in your own Library or Data Model class). |
A start event can only be created via the elements toolbar. |
Message Event |
The Message Event waits for a message with a defined content. You can use the message event in the Designer as an intermediate event or as a boundary event:
Plain Event, Message Event and Timer Event can be used as boundary events along with User Task and Receive Task. When using the events as boundary events, attach the element directly to the border of the corresponding task:
|
On Exit: Input message (define the corresponding type of message in your own Library or Data Model class). |
Trigger Events: Use the attribute Trigger Events in the Attributes Panel to define which button of a form associated to the element triggers the default process flow of a BPMN process. This attribute is only available for boundary events. |
Free Text |
The Free Text element allows the user to create an additional text field on the canvas, e.g. to display additional descriptions or notes. |
None. The content of this element is ignored during execution. |
- |
Exclusive Gateway |
Use the Exclusive Gateway to model a decision in the process. The process will continue with the sequence flow where the defined condition is true. You can also define a default sequence flow (see Particularity).
|
None. |
An exclusive gateway can have one outgoing flow that is marked as the Default sequence flow . This is the flow of the process that will be followed if all other conditions do not match. The default flow is marked with a slash on the relation:
You can mark a sequence flow as to be the default in the Attributes Panel:
|
End Event |
The End Event marks the end of a process. If the process consists of several branches, all other open branches continue to run to their end. Every process branch needs its proper end event. |
On Event: Without input or output parameters. |
- |
Lane |
Use the lane element to design role-based processes. Assign one or multiple roles to a lane element and model all the steps that the assigned role(s) has/have to perform within that lane. |
None. |
- No labels