Skip to main content
For more details about creating cases, see Creating a case with a workflow. A configured workflow for processing multiple documents should look as follows: For a multi-document processing case that includes verification, the Workflow tab should look as follows: The Data Model tab should have the following fields (in addition to the required Attachments, BatchId, and VerificationUrl fields):
NameIdTypeOptions
AddressAddressField group (list)Data type: Address
BirthDateBirthDateText
CityCityText
ContractDateContractDateText
ContractNumberContractNumberText
DeliveryAddressDeliveryAddressText
EmployerNameEmployerNameText
FirstNameFirstNameText
HomePhoneHomePhoneText
InitialInitialText
InvoiceCompanyInvoiceCompanyText
InvoiceDateInvoiceDateText
InvoiceNumberInvoiceNumberText
InvoiceTableInvoiceTableField group (list)Data type: InvoiceTable
LastNameLastNameText
LetterDateLetterDateText
LetterFromLetterFromText
LetterToLetterToText
PriceCompanyPriceCompanyText
PriceTablePriceTableField group (list)Data type: PriceTable
SSNSSNText
TotalTotalText
WorkPhoneWorkPhoneText

​
Configuring a stage that will submit a document for processing

For more detailed instructions, see the Configuring workflow stages and Utility step sections.
  1. Open the Send for processing stage in configuration mode, replace the Edit details step with a Utility step, and specify the following name for this step: Send for processing.
  2. Open the Utility step and call the SendForProcessing activity. For more details about creating this activity, see SendForProcessing.
You can begin creating an activity by clicking the configuration button to the right of the Rule field. Alternatively, you can leave the pyUtilityStub value specified in the Rule field and come back to this step after you have created an activity set.
  1. In the CaseId field, specify the following: .pzInsKey.

​
Configuring a verification stage

For more detailed instructions, see the Configuring workflow stages and Utility step sections.
  1. Open the Verification stage in configuration mode, add a Utility step, and set its name to be Update Verification Url.
  2. Rename the Edit details step to Verification.
  3. Open the Update Verification Url step and call the UpdateVerificationUrl activity. For more details about creating an activity for a multi-document case, see UpdateVerificationUrl.
  4. Connect the Verification and Update Verification Url steps using a Verification flow action connector. For more information about creating a flow action, see Creating a flow action.
  5. In the CaseId field, specify the following: .pzInsKey.

​
Configuring a stage that will fetch the processing results

For more detailed instructions, see the Configuring workflow stages, Utility step, and Decision step sections.
  1. Open the Fetching captured data stage in configuration mode and delete the Edit details step.
  2. Add a Decision step and name it Batch stage is processed.
  3. Open the step and select Boolean Expression in the Type field.
  4. In the Expression field, enter or configure a @MultiDocumentBatchIsProcessed(.BatchId) condition. For more details about creating this function, see MultiDocumentBatchIsProcessed.
  1. Click Submit.
  2. Create a Utility step named Fetching Invoice data for the true branch and call the FetchingCapturedData activity. For more information about creating this activity, see FetchingCapturedData.
  3. Enter .pzInsKey in the caseId field and Invoice_eng in the templateName field.
  1. For the true branch, create a Utility step named Fetching Banking data and call the FetchingCapturedData activity.
  2. Enter .pzInsKey in the caseId field and Banking_eng in the templateName field.
  1. For the true branch, create a Utility step named Fetching Contract data and call the FetchingCapturedData activity.
  2. Enter .pzInsKey in the caseId field and Contract_eng in the templateName field.
  1. For the true branch, create a Utility step named Fetching Letter data and call the FetchingCapturedData activity.
  2. Enter .pzInsKey in the caseId field and Letter_eng in the templateName field.
  1. For the true branch, create a Utility step named Fetching Price data and call the FetchingCapturedData activity.
  2. Enter .pzInsKey in the caseId field and Price_eng in the templateName field.
  1. For the false branch, create a Utility step named Create Error and call the CreateError activity. For more details about creating this activity, see CreateError.
  2. Enter .pzInsKey in the caseId field. In the errorMessage field, enter the following text: “Please complete the verification task before proceeding.”