Page History
Include Page
How the process engine behaves when receiving a message event is completely dependent on what was modeled in the process module. There is no default action executed when receiving a message event. Examples of behavior that you can model include: Starting a new case or making a task available to the worklist, canceling a case, or placing information in the domain of the case.
Parameters
Name | Description | Type | Required | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Send to specific Case Ids | The id(s) of the receiving case(s). The specific caseId(s) do not have to be part of the message, but could be.
| Expression | falseNo | ||||||||||||
Case Ids Target Attribute | The case ids of the case affected by the message event are placed in the selected attribute. This attribute must be multivalued and of the type integer. | Multivalued integer | falseNo | ||||||||||||
Message event | The name of the message event that will be triggered. | Message event | trueYes | ||||||||||||
Values | These elements represent the content of the message. You have to specify what the result attributes will be. | Elements | falseNo |
DCM_ThrowMessageEvent vs DCM_ThrowAsyncMessageEvent
...
Overview
Content Tools