Overview
The Potential Layout Variations feature helps you identify Structured layout variations that can be created to reduce the number of submitted pages that do not match to any layout variation in the system. To find, identify, and create potential layout variations, you need to:
Make sure the prerequisites are met.
Find Potential Layout Variations.
Create layouts.
Submit samples.
Run a Potential Layouts job and identify missing layout variations.
Validate New Layouts.
Create new layouts.
Resubmit samples.
Review submissions.
Review the No Layout Variation Found section.
Review Transcription.
Step 1: Make sure the prerequisites are met
Before you proceed with running a Potential Layouts job, you have to align with the following requirements:
Potential Layouts jobs run in a separate trainer application. To learn more, see the What is the Trainer? article.
Prepare blank versions of the new layouts. Acquire all available variations of the new layouts.
Prepare completed samples of the new layouts. If possible, prepare ~500 samples with data for each layout.
To skip Supervision and QA tasks while submitting documents for a Potential Layouts job, we recommend using the following settings:
Administration > Settings
Submission Upload - Enabled
Flow Settings
Classification
Semi-structured Classification - Disabled
Semi-structured QA sample rate - 0%
Manual Classification Supervision - Disabled
General Transcription
Manual Transcription Supervision - Disabled
Transcription Quality Assurance - Disabled
Structured Document Transcription
Structured Text Minimum Legibility Threshold - 0
We recommend restoring the settings to their previous state once you have identified and created all new layout variations.
Step 2: Find Potential Layout Variations
Create layouts
To find potential layout variations, you need to create new layouts from the blank versions of the documents that you have prepared. You do not need to add fields to the layouts at this stage. When you’ve created all layouts, lock them and assign a release with them to a flow. To learn more about how to create Structured layouts and assign a release with them to flows, see Creating Structured Layouts, Build and Deploy a Layout, Adding a New Release, and Assigning a Release to a Flow.
Submit samples
Submit the completed samples with data by going to Submissions > Submissions, and then clicking Create Submission. Make sure to select One Submission per file when submitting the documents.
Run a Potential Layouts job and identify missing layout variations
Once the samples are successfully submitted, those that are not matched to any layout will appear in the Submissions > No Layout Variation Found section. To find Potential Layout Variations, follow the steps from the Potential Layout Variations article. The steps will help you:
Run a Potential Layouts job.
Review the job’s results.
Create the foundation of your new layouts by using the Manual Redaction feature.
Step 3: Validate New Layouts
Create new layouts
Add fields to the layouts you created in the previous Create layouts phase, and create new layouts, using the results from the Potential Layouts job. When you’ve created all layouts, lock them and assign a release with them to a flow. To learn more about how to create Structured layouts and assign a release with them to flows, see Creating Structured Layouts, Build and Deploy a Layout, Adding a New Release, and Assigning a Release to a Flow.
Resubmit samples
Resubmit the original set of samples you used in Submit samples, or submit a new subset of samples with data.
Review submissions
Once the submissions have finished processing you can identify the number of layouts still not matching and the machine extractions of the layout fields.
Review the No Layout Variation Found section
Go to Submissions > No Layout Variation Found and filter by Submission Date to see the most recent submissions. To see the impact of the new layouts that were built, you can compare the unmatched submissions count to the original No Layout Variation Found count. You can review pages that were not matched to any layout by clicking on the pages’ Page IDs. If the number of records in No Layout Variation Found is still large, you can re-run a Potential Layouts job on the new sample set to identify all missing layouts that may need to be built.
Review transcription
To review the machine transcriptions of individual documents:
Go to Submissions > Documents.
To open the Document Output page, click on a Document ID.
Select Exceptions from the drop-down menu on the right-hand side next to the search bar.
Look for an exception that states “Supervision Required, But Disabled”.
The exception “Supervision Required, But Disabled” appears for fields that would have been sent to Supervision if the Supervision functionality was enabled. To verify that the layouts’ designs do not negatively impact the automation:
Make sure that all boxes are properly positioned over the correct fields.
If certain boxes are not sized properly, make adjustments to the original layouts.
If the majority of the bounding boxes are misaligned on the document, this could mean that the submission might have been matched to an incorrect layout.
Make sure that you’re using the correct data types for all fields.
If certain fields are incorrectly transcribed, check what the expected characters are for their respective data types. To learn more, see Supported Characters and Default Data Types, Creating Data Types with a List of Expected Values, and Creating Data Types with Custom Patterns. If necessary, change the fields’ data types in the Layout Editor.
Make sure that Multiline is enabled where applicable.
If a field’s value spans over multiple lines, enable the Multiline setting for the field in the Layout Editor.
Check what the Transcription Supervision setting for a field is in the Layout Editor:
If a field’s Transcription Supervision setting is set to Always or Consensus, the field will always go to Supervision.
Note that a certain number of fields will continue to go to Supervision if the machine confidence is below the transcription threshold, even after making the above changes. The goal of applying the above changes is to identify fields where the field properties may have been incorrectly configured.