You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
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 BlueriqCaseModelling Library. It is only available when the case-engine-client profile is enabled.
The DCM_CaseCreate service can only be called from a scope where the dossier and metadata aggregate types are known. The CaseCreate will store the data from this application scope. Make sure that the application does not change for running cases, since the model from that application id (branch + projectname) is bound to the case from the start.
Parameters
| Name | Description | Type | Required | Direction |
|---|---|---|---|---|
| CaseCreateMessageEvent | The name of the message event that will be triggered to create the case. | Message event | Yes | Input |
| DossierAggregate | The Aggregate type that is used to store the dossier data of the case. | Aggregate | Yes | Input |
| MetadataAggregate | The Aggregate type that is used to store the metadata for the case. | Aggregate | Yes | Input |
| ProcessMapping | The process mapping to be executed after case creation. | Data Mapping | Yes | 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