You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
The AQ_NextTasksForMessageEvent service call type is used to determine if there is exactly one task available for the current user in the case(s) affected by the earlier thrown message event(s). If there is exactly one task available, this task will be activated and the service exits via the OneTask event. You can start this activated task automatically using the AQ_ExecuteTask service, without explicit selection of the task by the user. The list with affected cases is cleared when the user returns to the worklist.
There are 3 events:
- One: when the next task available is activated after the message event.
- Multiple: when there are more than one task available after the message event.
- None: when there is no task available after the message event.
Parameters
| Name | Description | Type | Required |
|---|---|---|---|
| caseIds | The case ids that were affected by a message event. Note: leaving the caseIds parameter empty is deprecated for the current DCM implementation and no longer supported in DCM 2.0 | Expression | Only required for DCM 2.0 |
| taskId | The attribute in which you want to store the task id. Note: leaving the taskId parameter empty is deprecated for the current DCM implementation and no longer supported in DCM 2.0 | Attribute | Only required for DCM 2.0 |
Overview
Content Tools