Node configuration

Best practices and details about all nodes configuration (tasks, gateways, events).

Best practices / Tips

All the included nodes of workflow and process must have a name (better to have a significant name) - the name helps to understand the process when checking the process design and while executing the process version - on the logs.

TASKS

To be used whenever an action is to be done by a user. When the process instance execution arrives at the User task node, a new task is created in the task list of the group(s) and/or user(s) assigned to that task. When assigned to a group, the task can be executed.

Automated activity executed when the process execution arrives to the task. The script is

An action can be added only if the related service is added. On the process version diagram, an Action node is identified by the service logo on the top left of the node.

To add an action, you have to click the icon in your properties panel - the available services are shown in the configuration panel, you can search by module or by action on the search

GATEWAYS

The functionality of the parallel gateway is based on the incoming and outgoing sequence flow(s):

  • fork: all outgoing sequence flows are followed in parallel, creating one concurrent execution for each sequence flow.

  • join: all concurrent executions arriving at the parallel gateway wait at the gateway until an execution has arrived for each of the incoming sequence flows. Then the process continues past the joining gateway.

Allows to make a decision based on data. Needs to have at least two segments that you can configure. Segments allows to apply conditions on the route. in the gateway cases, it allows to execute an extra action or to double check if the route taken is the good one.

FLOWS

The sequence flow is used to connect flow nodes in a process version. Conditions can be set when used with exclusive gateways.

EVENTS

The first node of the process version, is a start event. Only one Start event for each process version can be set. A start event can also be a start catch event (see below how to configure a Catching event).

A process leads to at least one end event. It can be a throw end event.

Event occurring between a start and an end event. The intermediate event can catch or throw event.

The throwing event allows to send an event value.

It can be intermediate or end event. Never a start event.

Catch an event from either another process or from a service event - it can be a partner event or an operator event.

It can be start or intermediate event. Never end event.

A signal can be only used once in a process version.

Last updated