Process

Process is a structured flow of activities or tasks that serve a particular business goal. In BPMN, a process is a central element that encompasses all associated elements, thereby illustrating the entire workflow and interactions within the business context.

Graphical Notation

A process does not have a visual representation. It can be wrapped into a pool to make the model clearer, but using pools isn’t mandatory.

XML Representation

In the XML, the process is represented by process element.

  <process id="new-process" name="New process" isExecutable="true" >
    . . .
  </process>

Properties

In the BPMN modeler, you can set the following properties of the process when no element is selected on the canvas:

Property

Description

Process id

The process id identifies the process when it is deployed. In runtime, it is called process key.

Name

The name of the process. The maximal length is 255 characters.

Candidate groups

A group of users permitted to start the process. If the user belongs to the group, they will see this process definition in the Start process view.

Candidate users

Individual users permitted to start the process. If the user is among candidates, they will see this process definition in the Start process view.

Event listeners

See listeners.

Signal definitions

To create a signal definition, set its Id, Name, and Scope:

  • Global signals are sent throughout the entire process engine. This means if one process instance triggers a signal event, other process instances can respond to it. This is useful for communication between different processes.

  • Process instance signals only function within their own process instance. They can help synchronize tasks that are mutually exclusive.

You can configure a signal event element to reference a definition.

Message definitions

To create a message definition, set its id and name. This message can be used in Message event elements.

Error definitions

To create an error definition, set its id and name. Besides, you may set Error code. This error can be used in Error event elements.

Escalation definitions

To create an escalation definition, set its Id and Name, and optionally Escalation code. Throwing and catching escalation events refer to the definition and match each other by its code. See Matching Escalations.

Since Jmix 3.1

History level

The history level for instances of this process: None, Instance, Task, Activity, Audit, or Full. Default means that the history level of the process engine is used. See History Levels.

Since Jmix 3.1

Documentation

A description and additional information about the element.