Many document types include tables to organize information. Appian can extract this information efficiently and present it in a reconciliation task to confirm it did so properly. If a user finds that the table was incorrectly detected, they can now manually draw the boundaries to extract the information as intended.
This page describes how to reconcile data extracted from tables, as well as the steps to draw a table boundary for extraction in case the service doesn't parse the data in the table correctly.
You'll reconcile table data as part of the overall doc extraction reconciliation task.
As users submit document extraction tasks, Appian will learn the aliases for your tables' column headers. It can then use the learnings to automatically extract table values, reducing the need for human reconciliation.
When manually extracting table data, users can take a variety of actions by clicking on the menu icon next to a column or row.
For columns, users can:
For rows, users can:
Users can also remove individual rows by clicking the close icon on the right side of each row
When extracting data from documents, you may find that some tables aren't correctly identified. Or, when the table is identified correctly, the table's columns or rows were split incorrectly. When this happens, Appian has trouble automatically extracting the information and presenting it in a reconciliation task.
Rather than manually fixing this data field by field, Appian lets you draw the boundaries of a table for more precise data extraction. After you draw the table boundaries, Appian will extract data from the selected location. The table reconciliation task shows a more accurate picture of the data.
You'll need to manually draw these tables in each document where they aren't correctly identified.
To draw table boundaries in a reconciliation task:
Review the updated data:
On This Page