Error Event
1. Overview
An Error Event is an event initiated by a certain error. Using Error Event allows the business process model to react on events within a task (business-error) and trigger alternative ways of process execution.
During BPMN-modelling, only business-errors are processed. They are different from Java-exceptions, which are processed in another way by default. |
- The following Error Event types are used in the modelling:
-
-
Error End Event — an event modelled at the end of a business process, or subprocess.
-
Error Sub-Process Interrupting Start Event — an event modelled at the initiation of subprocess start with a business-error.
-
Error Boundary Interrupting Intermediate Event — an event modelled at the boundary between a container and a transactional subprocess or task.
-
2. Modelling Error End Event
To model and configure an Error End Event, take the following steps:
-
Model all the required business process activities.
-
Add an end event to the business process.
-
Select Error End Event in configuration.
-
On the General tab, configure the element:
-
In the
Id
field, enter element identificator, or leave default value. -
In the
Name
field, enter element name.
-
-
Expand the Details block by clicking
+
.
-
In the
Name
field, enter error name. For example,errorNoValid
. -
Optionally, in the
Code
field, enter error variable. For example,codeErrorNoValid
. -
In the
Global Error referenced
field, select error element link.Values in this field are set automatically and corresponds to the error name defined in the
Name
field. In this case —errorNoValid
.If error code variable is also defined,
Global Error referenced
value will also be set automatically, according to the defined code.In our case, the value will be:
errorNoValid (code=codeErrorNoValid)
.
-
Optionally, in the
Message
field, enter error data (description) that will be sent by the system.
If the Error End Event element sends an Error Sub-Process Interrupting Start Event or Error Boundary Interrupting Intermediate Event signal to the receiving element, then This connection is not necessary, but rather can be called for by the business process specifics, as Error Sub-Process Interrupting Start Event and Error Boundary Interrupting Intermediate Event can be initiated by a business-error that appeared during task (user task, service task, etc.) execution. |
3. Modelling Error Start Event for a subprocess
Error Start Event modelling process is described in the following document.
4. Modelling Error Boundary Interrupting Intermediate Event
Error Boundary Interrupting Intermediate Event modelling process is described in the following document.