ProcessModeler Step Types
The DigitalSuite ProcessModeler is a tool that allows you to design, develop, and test processes.
A process is composed of a number of connected steps. A step can be an Activity, an Event, or a Gateway.
Steps are dragged onto the design grid and snap into place at the intersection of the bold grid lines.
In composite APIs, you can use a subset of the process step types. Manual Activity and Subprocess Activity are not available for composite APIs.
This document describes each step that can be used in process designs.
Activities are tasks that take place during the execution of a process. They are represented by rectangles. An icon within the rectangle represents the type of activity.
This activity does not have a specific function, it is usually used for data mapping activities.
This activity calls a connector or composite API.
|Email / Notification Activity
This activity sends an email or a mobile notification.
This activity assigns a task to a user or a group of users, for example the approval or rejection of a request.
This activity will run a subprocess.
Events signify that something has happened. They are represented by a circle. An icon within the circle represents the type of event.
The event that starts the process. Start events are represented by a circle with a single, narrow border.
An empty circle represents a process that is triggered by submitting a form.
|Message Start Event
This process is triggered when an email is sent to an auto-generated email address. The information contained in the email is mapped to process input variables.
|Timer Start Event
This process is triggered automatically at a defined frequency.
|Conditional Start Event
This process is triggered if a condition is met (evaluates to
Process Flow Events
These events occur during the flow of the process; they are represented by a circle with a double border.
The process pauses for the duration of the time specified in the timer event.
The process pauses until a condition that is evaluated by a composite API is met. The process continues when the composite API returns
Intermediary events are a special type of event that triggers when something outside of the ordinary happens within an activity; for example, a timeout error. These events trigger the execution of an alternative process branch to manage the problem.
Within the process design, intermediary events are represented by a small circle with a double border located on a corner of the activity. They are added to an activity from the contextual menu which appears when the activity is selected.
|Error Intermediary Event
The alternative branch is followed if the activity fails.
|Timer Intermediary Event
The alternative branch is followed if the activity does not complete within the time specified in the timer.
|Cancel Intermediary Event
The alternative branch is followed if the activity is cancelled.
End events denote the termination of a process; they are represented by a single bold border. Every process must have an end event. All branches must either rejoin the main process flow or terminate with their own end event.
Gateways are decision points within the process; they are represented by diamonds. They determine the path of the process flow depending on conditions.
This gateway represents concurrent activities in a process. Each activity is performed independently of each other, in parallel. The different paths can rejoin the main flow following execution using an And Join, or each branch can end independently with an end event.
This gateway enables branches that have split, maybe due to an And Split or an intermediary event, to rejoin following their execution.
|Exclusive Or Split
An Exclusive Or Split gateway evaluates a condition and uses the result to determine which of the mutually exclusive branches to follow.
|Exclusive Or Join
An Exclusive Or Join enables branches that have split due to an Exclusive Or Split gateway to rejoin following their execution.