Description:

The Get Text from Receipt workflow step processes a receipt form document and stores the resulting receipt form text in the specified Variable or Global variable.

The step supports:

• Specifying the receipt form document path.
• Storing the receipt form text in a Variable or Global variable.
• Using the extracted text in subsequent workflow activities.
• Returning a True result when the operation succeeds.
• Return False when the operation does not succeed.
• Incorporating receipt-document text extraction into workflow automation.

Usage:

The Get Text from Receipt step is typically placed after a workflow has obtained or generated a receipt form document.

The workflow supplies the receipt form path to the step. The step processes the document and stores the resulting receipt form text in the configured Variable or Global variable.

A typical workflow pattern is:

Get Receipt Document → Get Text from Receipt → Process Receipt Text

The resulting text can then be used by subsequent workflow activities to:

• Store receipt-related text.
• Pass receipt text to another workflow activity.
• Perform additional text processing.
• Prepare information for downstream processing.
• Generate notifications or workflow output.
• Perform additional analysis or validation.

To use this step, set up an Azure ML service in the FlowWright application. Go to the Status > Settings > Configuration page. Select the Azure ML category from the drop-down menu. Click here to learn more about the Azure ML and Cognitive Service subscription. 

A sample Azure ML configuration is provided here for reference. 

Typical Workflow Suggestions:

Extract Text from an Uploaded Receipt

Use the step after a receipt document has been uploaded or made available to the workflow.

Example:

Upload Receipt → Get Text from Receipt → Process Receipt Text

The receipt path is supplied to the step, and the resulting text is stored in a Variable or Global variable.

Process Receipt Documents from a Folder

Use the step when a workflow processes receipt documents obtained from a predefined document location.

Example:

Get Receipt File → Get Text from Receipt → Process Extracted Text

The workflow can pass the appropriate receipt form path to the step and use the stored text in subsequent processing.

Store Receipt Text for Subsequent Workflow Activities

Use the step when the extracted receipt text needs to remain available to multiple downstream activities.

Example:

Receipt Document → Get Text from Receipt → Store/Process Receipt Text

The Variable/Global to store the receipt form text property provides the destination for the resulting text. clsAzureMLReceiptRecognizer

Route the Workflow Based on Text Extraction

Use the True and False return paths to control what happens after the receipt document is processed.

Example:

Get Text from Receipt → True: Continue Processing / False: Handle Failure

The success path can continue receipt processing, while the False path can connect to an appropriate alternative or error-handling activity.

Prepare Receipt Text for Downstream Processing

Use the step as an intermediate activity before another workflow operation requires the receipt text.

Example:

Retrieve Receipt → Get Text from Receipt → Text Processing → Continue Process

The extracted text stored in the configured Variable or Global variable can be passed to subsequent workflow activities.

Example:

Let’s build and execute the “clsAzureMLReceiptRecognizerDef” example. 

• Create a new process definition named “clsAzureMLReceiptRecognizerDef” and open it in designer mode. 
• Drag a "clsAzureMLReceiptRecognizer" step to the canvas.
• Connect the dots between the “Start” and “clsAzureMLReceiptRecognizer” steps, as shown above. 
• Select the line between the steps to configure the “Connection Properties”. The default property values are “None, True, False, Error, and Evaluate”. Depending on the step’s purpose, you can configure additional values.
• Define a variable or a global to store the result.
• Click the "clsAzureMLReceiptRecognizer" step to configure its "Required" properties. Provide a name for the step. Provide the path to the receipt image. Provide a variable or global reference to store the result. Click the Save button. Note: Click the "AI Predict" button for Copilot to add new process steps that match your process description. 

• The “Logging” configuration is necessary for documentation and to measure workflow progress and percent complete. This is done by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.

• Create a new process instance and execute it. When the workflow reaches the Get Text from Receipt step, the configured receipt form path is processed, and the resulting receipt form text is stored in the specified Variable or Global variable. Use the stored value in subsequent workflow activities.

Tips:

• Provide a valid receipt form path before the step executes.
• Use a meaningful Variable or Global name for the extracted receipt text, such as receiptText.
• Verify that the document referenced by the receipt form path is available to the workflow.
• Keep the receipt document location consistent across deployment environments.
• Connect the True path to the next processing activity.
• Connect the False path to appropriate alternative or error-handling logic.
• Test the workflow with representative receipt documents before deployment.
• Verify the resulting Variable or Global value before using it in downstream activities.
• Avoid assuming that the extracted text contains particular receipt fields unless that behavior has been validated for the FlowWright implementation.
• When receipt information is passed to downstream systems, apply appropriate handling for sensitive or business-related information.

Definition Sample:

You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page. 

Note: After the import, verify and complete any missing configurations, such as file path references and database connections. Then, save the definition to confirm the changes. 

Click here to download the sample file.