Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

W-16684543 prompt settings #46

Open
wants to merge 1 commit into
base: W-16684499-einstein-doc-action
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions modules/ROOT/pages/document-processing.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,24 @@

Before you analyze documents with IDP, you must create and publish document actions, the configurable schema definitions containing the necessary instructions to process your documents.

After you publish a document action to Anypoint Exchange, you can programatically call the IDP API to execute the document action and extract data from a document. As a result, the document action analyzes the provided document and returns a response in JSON format with all the extracted fields. You can query the IDP API to check the status of an execution at any time.
After you publish a document action to Anypoint Exchange, you can programmatically call the IDP API to execute the document action and extract data from a document. As a result, the document action analyzes the provided document and returns a response in JSON format with all the extracted fields. You can query the IDP API to check the status of an execution at any time.

== Document Actions

include::partial$document-action.adoc[tag=definition]

IDP provides preconfigured *Invoice* and *Purchase Order* templates for creating custom document actions. Each template provides a set of expected fields to extract from the document into a structured response. When creating a new document action, choose the type that aligns best with the document to process. For example, the *Invoice* type can process invoices, receipts, and similar documents. If none of these types align with your documents, use the *Generic* type to fully customize the fields to extract by asking questions in natural language.
IDP provides the preconfigured Invoice and Purchase Order templates for creating custom document actions. Each template offers a set of expected fields to extract from the document into a structured response. When creating a new document action, choose the type that aligns best with the document to process. For example, the Invoice type can process invoices, receipts, and similar documents. If none of these types align with your documents, use the Generic type to fully customize the fields to extract by asking questions in natural language.

After you create a document action, publish it to Anypoint Exchange to make it available for consumption from RPA and through the IDP API.

=== Enhance Data Extraction With Einstein

When you create a Generic type document action, you can select whether to use Einstein to analyze and extract data from your document. Einstein can answer complex questions that require further analysis of the document instead of just searching and extracting a field. For example, you can ask Einstein what's the total amount due in an invoice after deducting taxes and other values from the document.

Use Einstein to analyze unstructured and semi-structured documents that don't use a standard format or are difficult to read without performing a complex analysis of the extracted data.

For configuration and usage instructions, see: xref:analyze-documents-with-einstein.adoc[].

== Reviews

Document actions return a JSON response that contains the extracted fields and their detected values. Each of these values has a confidence score that determines the accuracy of the value during the extraction.
Expand Down
6 changes: 1 addition & 5 deletions modules/ROOT/pages/index.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -10,11 +10,7 @@ The confidence score represents the probability that IDP has properly extracted

Each processed document shows a confidence score for each extracted field. When this value is lower than the defined threshold, IDP sends the document for review by a human to verify the accuracy of the extracted values. You can add single reviewers or teams to each document action.

== Enhance Data Extraction With Einstein

When you add prompts to your document actions, you can select wether to use the default or Einstein's response. Einstein can answer complex questions that require further analysis of the document instead of just searching and extracting a field. For example, you can ask Einstein what's the total amount due in an invoice after deducting taxes and other values from the document.

Use Einstein to analyze documents that don't use a standard format or are difficult to read without performing a complex analysis of the extracted data.
You can use Einstein to analyze semi-structured or unstructured documents and enhance the data extraction process.

== See Also

Expand Down