You are viewing the documentation for Blueriq 14. Documentation for other versions is available in our documentation directory.
This service call is part of the ongoing effort to support more DCM features natively in the Blueriq Runtime. Its signature and behavior may change over time. Please check release notes and upgrade instructions when using it.
This service call definition is part of the DCM library. It is only available when the case-engine-client profile is enabled.
The DCM_CaseCreate service call type will be used to signal the Case Engine to create a case at the end of an intake flow. For now, it publishes the required data to an AMQP queue. The Case Engine will read the message from the queue and create a case.
Due to the asynchronous nature of this call, no data is returned. The case will show up in Aggregate Lists and/or Case Lists once it has been created.
This service call definition is part of the DCM library. It is only available when the case-engine-client profile is enabled.
Parameters
| Name | Description | Type | Required | Direction |
|---|---|---|---|---|
| CaseCreateMessageEvent | The name of the message event that will be triggered to create the case. | Message event | true | input |
| CaseStartMessageEvent | The name of the message event that will be triggered to start the case. | Message event | true | input |
| CaseStartMessageEventCaseIdParameter | The name of the parameter in the CaseStartMessageEvent that indicates the id of the case to start. | String | true | input |
| CaseDataAggregate | The Aggregate type that is used to store the data of the case. | Aggregate | true | input |
| AggregateReferenceEntity | The entity that is created to store a reference to the Case Data Aggregate. Note: this entity type is expected to be part of the Case Aggregate . | Entity | true | input |
| CaseDataAggregateTypeAttribute | The attribute within the AggregateReferenceEntity that will store the Case Data Aggregate type. | Attribute | true | input |
| CaseDataAggregateIdAttribute | The attribute within the AggregateReferenceEntity that will store the Case Data Aggregate ID. | Attribute | true | input |
| CaseDataAggregateVersionAttribute | The attribute within the AggregateReferenceEntity that will store the Case Data Aggregate version. | Attribute | false | input |
| CaseAggregate | The Aggregate type that is used to store the metadata for the case. | Aggregate | true | input |
| ProcessIdAttribute | The attribute in which the id of the created process will be stored. Note: this attribute should be present in a singleton entity that is part of the Case Aggregate. | Attribute | true | input |
Example
This picture shows how the parameters would be filled for the DCM Foundation project.
Properties
See Case Engine Client Properties for explanation on how to configure the queue.
Overview
Content Tools
4 Comments
Geert Graat
Since we can only select an entity here (instead of an expression), should this always be a singleton? Then we should point that out here.
Felix Janssen
It's not a singleton in the DCM Foundation. An instance is created when storing the Case Data Aggregate. In theory, there can be multiple Case Data Aggregates present, each with a different type, so there can be multiple references.
Felix Janssen
Because we only support one reference, we could change the DCM Foundation, but that would also hit the non-intake parts of the project.
So that's something for a later moment.
Felix Janssen
Removed 'Target' from the name