Testing your learning instances before moving them to production ensures that such learning instances meet your expectations in terms of the performance, quality, and reliability of the extracted data.

As a Document Automation developer, you can use the Test mode option in learning instances to try different settings, such as using different OCR providers, generative AI providers, different generative AI prompts, and turning validation feedback on or off.

Benefits

Track all changes using versions and extraction results in a single console
A single console for developers to track all changes as versions for learning instances and assess their impact of changes on extraction results.
Compare results across versions
Developers can compare extraction results across versions and can compare output after each change. For example, comparing extraction results with generative AI option enabled or disabled. This way developers can choose the most optimal learning instance settings.
Quicker testing cycles
30% faster development experience due to optimizations that significantly reduce time to process each page for developers. This enable quicker development cycles by reducing the time required for testing significantly.

End-to-end workflow

The following image shows the workflow of how a learning instance is tested in the Dev environment before moving it to the UAT environment:

End-to-end workflow of testing learning instances in the Dev environment
  1. Create or edit an existing learning instance. See Create a learning instance in Document Automation.
  2. Enable test mode for the learning instance. See Enable test mode for learning instances.
  3. Configure the learning instance and save the changes. See Create a learning instance in Document Automation.

    A new version is created whenever you make changes to the learning instance configuration.

  4. Process sample documents to validate data extraction results. See Process documents in test mode.
  5. Validate the processed document to check if the data is extracted as expected. See Validate documents in test mode.
  6. Compare the data extracted from different versions of the learning instance to find any configuration changes that might improve data extraction. See Compare versions of a learning instance.
  7. Repeat step 3 through step 6 until you get the desired results.
  8. After you get the desired results, export the learning instance from the development (Dev) environment and import it into the UAT environment. See Export and import learning instances.

    Perform an end-to-end testing of the learning instance in the UAT and Prod environments before moving it to production. See Publish the learning instance to production.

    Note:
    • Version history is not imported when you export and import learning instances from one environment to another.
    • If you are using validation feedback and if you want to use this feedback for testing, ensure that you synchronize (sync) the learning instance from Prod to UAT and Dev environments before starting new development.