Stage For Store Case Document
Stages a new case for storage in the persist system. The document will be staged in the current transaction to be committed once all commits have been triggered.
Widget
Configuration
Fill in the following fields:
Description: Allows changing the name that appears on the widget. This may be useful to quickly find a particular widget or distinguishing it from other similar shovel operation widgets when building large flows.
Shovel Operation: The name of the Shovel Operation. Pre-configured to StageForStoreDocument.
caseType: The case type to add the document into. (See Section : “CaseTypes, DocTypes, and Status Events”)
caseId: The Shovel Expression that will pull the case ID from the Context Document, referring to the caseIdDestination (See Section : “Stage For Store Case”)
Example shovel operation:
atFieldRead(fieldReference("builtin:document/caseId"),readField(fieldReference("builtin:key/data")))docType: The type of document to add. (See Section : “CaseTypes, DocTypes, and Status Events”)
documentName: The name of the document that will be created and added to the Context Document.
includeMetadata: If true, this will persist the document metadata along with the document data. If false it will only persist the document data.
status: The initial status of the document. (See Section : “CaseTypes, DocTypes, and Status Events”)
parentDocType: The type of the parent document to link to the document (e.g., AdjudicationRequest) (See Section : “CaseTypes, DocTypes, and Status Events”) (Optional)
caseFileReferenceId: The ID of the file where this entity is derived from. (Optional)
lookupFieldsDocumentName: The name of the document in the Context Document that the lookup fields come from.
documentIdDestination: The name of the Context Document where the ID of this document will be saved.
If necessary, click the Notes tab and enter any relevant information.
Click Save.
The widget will be marked with a green check.
