Page History
| Include Page | ||||
|---|---|---|---|---|
|
With the DCM_ThrowMessageEvent service call, you can throw Message event towards the process engine. You can select a message event which you have previously defined in the process module. For every defined data field, you can define an expression to fill the field with information. The context of this expression is the module in which you place this service.
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 | false | ||||||||||||
| 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 | false | ||||||||||||
| Message event | The name of the message event that will be triggered. | Message event | true | ||||||||||||
| Values | These elements represent the content of the message. You have to specify what the result attributes will be. | Elements | false |
DCM_ThrowMessageEvent vs DCM_ThrowAsyncMessageEvent
The DCM_ThrowAsyncMessageEvent is also available. As the name suggests, that service works asynchronously as opposed to this service which is synchronous. The benefit of using the asynchronous service is that a user does not have to wait for the message event to be processed, which could take some time if the message event is broadcast to a lot of cases. The downside of the asynchronous service is that you no longer receive the affected case ids, as you do not have to wait. So consider carefully which service you need for your use case. It's also possible to broadcast a message event to all listening cases using the DCM_ThrowAsyncMessageEvent, this is not possible using the synchronous service call.
...
Overview
Content Tools