document-understanding
2024.10
true
- Overview
- Getting started
- Building models
- Consuming models
- Automations in Document Understanding™
- Activities
- API calls
- Model Details
- 1040 - ML package
- 1040 Schedule C - ML package
- 1040 Schedule D - ML package
- 1040 Schedule E - ML package
- 1040x - ML package
- 3949a - ML package
- 4506T - ML package
- 709 - ML package
- 941x - ML package
- 9465 - ML package
- ACORD125 - ML package
- ACORD126 - ML package
- ACORD131 - ML package
- ACORD140 - ML package
- ACORD25 - ML package
- Bank Statements - ML package
- Bills Of Lading - ML package
- Certificate of Incorporation - ML package
- Certificate of Origin - ML package
- Checks - ML package
- Children Product Certificate - ML package
- CMS 1500 - ML package
- EU Declaration of Conformity - ML package
- Financial Statements - ML package
- FM1003 - ML package
- I9 - ML package
- ID Cards - ML package
- Invoices - ML package
- Invoices Australia - ML package
- Invoices China - ML package
- Invoices Hebrew - ML package
- Invoices India - ML package
- Invoices Japan - ML package
- Invoices Shipping - ML package
- Packing Lists - ML package
- Payslips - ML package
- Passports - ML package
- Purchase Orders - ML package
- Receipts - ML Package
- Remittance Advices - ML package
- UB04 - ML package
- Utility Bills - ML package
- Vehicle Titles - ML package
- W2 - ML package
- W9 - ML package
- Public endpoints
- Supported languages
- Insights dashboards
- Data and security
- Licensing and Charging Logic
- How to
Document Understanding Modern Projects User Guide
Last updated Nov 11, 2024
Automations in Document Understanding™
There are several ways in which you can consume Document
UnderstandingTM
capabilities:
- The DocumentUnderstanding.Activities package is available in Studio Web, Studio X, and Studio Desktop and is pre-configured for you either when you create a new automation starting from a file, or if you continue your journey after publishing a project version.
- Using the IntelligentOCR package, which is designed for Windows and Windows Legacy projects, and pre-configured in the Document Understanding process template.
- Using API calls, consuming Document Understanding as a service via the programming language of your choice.
Check the table below to select the optimal automation method that aligns efficiently with your needs and works best for your projects.
| IntelligentOCR activities package | DocumentUnderstanding.Activities package | Document Understanding APIs | |
|---|---|---|---|
| Deployment |
| Automation Cloud™ | Automation Cloud™ |
| Best suited for | RPA developers |
| Users with previous programming experience |
| Integrated development environment (IDE) | Studio Desktop |
| IDE of your choice |
| Benefits |
|
|
|
| Drawbacks |
| Compared to IntelligentOCR, there are some missing features, which are planned to
be added:
|
|
| Use case | Use if you have an existing automation relying on it for which adopting DocumentUnderstanding.Activities is either impossible (functionality currently not available), or costly. | Use this package if you are just getting started with Document Understanding. Use
for new automations relying on:
| Use API calls if you want to integrate our services seamlessly into your applications and systems. Use APIs to integrate Document Understanding in microservices architectures which are integrated as software as a service (SaaS). |
