Data Lookup and Validation with Flow Blocks

  • Published on Mar 18, 2025
  • 2 minute(s) read

Overview

To minimize Supervision and increase automation, you can use data lookups and validations. Each flow can be configured to pull and validate data, using Custom Code Blocks, Database Blocks, and API Blocks. To learn more about these blocks, see Flow Blocks.

You can configure flows in a flexible way that allows you to:

  • have full control over which fields and table cells are processed within particular blocks and the logic used to process them

  • populate fields and table cells with values from external sources

  • perform data validations as part of extraction in Hyperscience

If you’re interested in the above-mentioned capabilities of the platform, contact your Hyperscience representative for more information.

Use Cases

The below use cases are just a couple of examples of how you can minimize Supervision and increase automation. You can define your own custom code logic and combine it with Database and API Blocks to build custom flows, according to your business needs.

Field “Required” but Blank

FieldRequiredButBlank.png

You can define Supervision logic for fields that are marked as “Required” during layout creation. For example, if INVOICE_NUMBER is a required field and the machine can’t identify it during Machine Identification, you can add a Custom Code Block to force the missing field to Field ID Supervision:

  1. If INVOICE_NUMBER is not identified, force the field to Field ID Supervision.

    1. You are asked to manually identify INVOICE_NUMBER.

      1. If INVOICE_NUMBER can’t be identified, mark the document as “Not in good order”.

      2. If INVOICE_NUMBER is identified, proceed with Field ID Supervision for the remaining fields.

  2. If INVOICE_NUMBER is identified, proceed with the default Supervision logic.

The above custom code logic saves you time by marking the document as “Not in good order” without having to go through Supervision for all fields. 

Data Lookup and Validation

DataLookupAndValidation.png

You can skip Transcription Supervision by validating a field’s value outside of Hyperscience. To achieve that, you can add a Custom Code Block that reaches an external database or an API endpoint to look up and validate a field’s value. If the value is validated, this field skips Transcription Supervision. If the value is not validated, the field is sent to Transcription Supervision.

Auto-populate

AutoPopulate.png

You can auto-populate fields by combining a Custom Code Block with a Database Block or an API Block. For example, you can define:

  • INVOICE_NUMBER as the lookup field

  • VENDOR NAME and VENDOR ADDRESS as the fields to be auto-populated 

The flow will only try to transcribe INVOICE_NUMBER, even though all fields will be identified. Once INVOICE_NUMBER is transcribed:

  • The Database or API Block will use the INVOICE_NUMBER to find the related fields that should be auto-populated.

    • If VENDOR NAME and VENDOR ADDRESS are found, auto-populate the fields and do not extract them in the upcoming blocks.

    • If VENDOR NAME and VENDOR ADDRESS are not found, proceed with the next steps in the flow.