You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Did you know that it is not allowed to send message events from within your process to process instances of the same type?

The process engine is based on the BPMN 2.0 specification. Therefore the process engine handles message events the same way BPMN 2.0 specifies. This article explains how BPMN 2.0 specifies message events and how Blueriq implements this specification.

BPMN modeling elements

This section gives an overview of the BPMN modeling elements (source: BPMN 2.0 specification) that are used in the example in the next section.

 

 

 

BPMN modeling elements plotted on Blueriq concepts

The following table shows the BPMN modeling elements plotted on Blueriq concepts.

BPMNBlueriq
EventEvent
TaskTask
Collapsed Sub-ProcessProcess
Normal flowProcess line
Message flowMessage event
PoolCase
LanesRoles

BPMN example

The example shows a collaboration with two pools. The two pools communicate through message flows with each other.

Blueriq example cases

The collaboration is split in two cases that still talk to each other via message events

 

 

BPMN message flow

BPMN defines a message flow as following (source: BPMN 2.0 specification):

 

Blueriq message event

It is not allowed to send a message event from within a process to a process with the same type.

Known issues

Issue numberIssueExpected fix version

BQ-3171

It is possible to use the AQ_ThrowMessageEvent service in a task to send a message to a process with the same type. Studio doesn't give a validation error on thisR11
BQ-3219Throwing a message event to a process with a started task that doesn't apply case locking leads to a double tasks in the database.R10
BQ-3220User ends a task, without case locking, while other user has a task, without case locking, started. This leads to a double task in the database.R10
  • No labels