> ## Documentation Index > Fetch the complete documentation index at: https://docs.abbyy.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a single-document processing case > Set up a Pega single-document case: define data-model fields and configure the send-for-processing and fetch-results stages that call FlexiCapture activities. A single-document processing case with verification needs the standard case fields plus the invoice fields, and two configured workflow stages. For the general procedure, see [Create a case with a workflow](/flexi-capture/connectors/pega/pega-add-case-type). Screenshot of the Workflow tab in Pega Dev Studio showing the single-document case life cycle with the Invoice received, Send for processing, Verification, and Fetching captured data stages and their steps. ## Data model fields Add the following fields on the **Data Model** tab, in addition to the required **Attachments**, **BatchId**, and **VerificationUrl** fields: | Name | Id | Type | Options | | ------------- | --------------- | ------------------ | -------------------- | | City | `City` | Text | | | Country | `Country` | Text | | | Currency | `Currency` | Text | | | InvoiceDate | `InvoiceDate` | Text | | | InvoiceNumber | `InvoiceNumber` | Text | | | Line Items | `LineItems` | Field group (list) | Data type: Line Item | | Total | `Total` | Text | | For the **Line Items** data type, see [Data types for a single-document processing case](/flexi-capture/connectors/pega/pega-one-doc-data-type). Screenshot of the Data model tab in Pega Dev Studio showing the single-document case fields City, Country, Currency, InvoiceDate, InvoiceNumber, Line Items, and Total alongside the required Attachments, BatchId, and VerificationUrl fields. ## Configure the stage that submits a document for processing For the general procedure, see [Configure the workflow stages](/flexi-capture/connectors/pega/pega-stages-config) and [The Utility step](/flexi-capture/connectors/pega/pega-stages-config#2). Open the **Send for processing** stage in configuration mode, replace the **Edit details** step with a **Utility** step, and name the step `Send for processing`. Open the **Utility** step and call the `SendForProcessing` activity. Start creating the activity by clicking the configuration button to the right of the **Rule** field. Alternatively, leave the `pyUtilityStub` value in the **Rule** field and come back to this step after you have created the activity set. For more information, see [SendForProcessing](/flexi-capture/connectors/pega/pega-send-for-processing-1). In the **CaseId** field, specify `.pzInsKey`. Screenshot of the SendForProcessing_Flow diagram and Utility step properties in Pega Dev Studio showing the Send for processing utility calling the SendForProcessing activity with .pzInsKey in the CaseId parameter. ## Configure the stage that fetches the processing results For the general procedure, see [Configure the workflow stages](/flexi-capture/connectors/pega/pega-stages-config) and [The Utility step](/flexi-capture/connectors/pega/pega-stages-config#2). Diagram of the FetchingCapturedData_Flow process in Pega Dev Studio showing a Batch stage is processed decision that branches on its true path to a Fetching captured data step and on its false path to a Create Error step. Open the **Fetching captured data** stage in configuration mode and delete the **Edit details** step. Add a **Decision** step and name it `Batch stage is processed`. Open the step and select **Boolean Expression** in the **Type** field. Specify or configure a `@SingleDocumentBatchIsProcessed(.BatchId)` condition in the **Expression** field. For the function itself, see [SingleDocumentBatchIsProcessed](/flexi-capture/connectors/pega/pega-func-one-doc#singledocumentbatchisprocessed). Screenshot of the Decision step properties in Pega Dev Studio showing the Batch stage is processed decision with Boolean Expression selected and the @SingleDocumentBatchIsProcessed(.BatchId) expression entered. For the `true` branch, add a **Utility** step named `Fetching captured data`. Open it, call the `FetchingCapturedData` activity, and specify `.pzInsKey` in the **CaseId** field. For more information, see [FetchingCapturedData](/flexi-capture/connectors/pega/pega-fetching-captured-data-1). Screenshot of the Utility step properties in Pega Dev Studio showing the Fetching captured data step calling the FetchingCapturedData activity with .pzInsKey in the CaseId parameter. For the `false` branch, add a **Utility** step named `Create Error`. Open it, call the `CreateError` activity, and specify `.pzInsKey` in the **caseId** parameter field. In the **errorMessage** field, enter this text: ```text theme={null} Please complete the verification task before proceeding. ``` For more information, see [CreateError](/flexi-capture/connectors/pega/pega-create-error-1). Screenshot of the Utility step properties in Pega Dev Studio showing the Create Error step calling the CreateError activity with .pzInsKey in caseId and the verification reminder text in the errorMessage parameter.