# Automations in Document Understanding™

> There are several ways in which you can consume Document Understanding<sup>TM</sup> capabilities:

There are several ways in which you can consume Document Understanding<sup>TM</sup> 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 cloud API calls, consuming Document Understanding as a service via the programming language of your choice.

## Choosing the right automation

Check the following table to select the optimal automation method that aligns efficiently with your needs and works best for your projects.

 <caption>
  Table 1. Choosing automations
 </caption>
 <colgroup>
  <col/>
  <col/>
  <col/>
  <col/>
 </colgroup>
 
  
    &nbsp; 
    IntelligentOCR activities package 
    DocumentUnderstanding.Activities package 
    Document Understanding Cloud APIs 
  
 
 
  
    Deployment 
   
      
         Automation Cloud&trade; and Test Cloud 
         Automation Suite 
         Standalone 
      

   
      
         Automation Cloud&trade; and Test Cloud 
         Automation Suite 
      

   
      
         Automation Cloud&trade; and Test Cloud 
         Automation Suite 
      

  
  
    Best suited for 
    RPA developers 
   
      
         RPA developers 
         Citizen developers 
      

    Users with previous programming experience 
  
  
    Integrated development environment (IDE) 
    Studio Desktop 
   
      
         Studio Desktop 
         Studio X 
         Studio Web 
      

    IDE of your choice 
  
  
    Benefits 
   
      
         Flexibility   You can modify the taxonomy and extraction results at runtime using custom code. 
      

      Extensible and open framework   You can bring your own classifier, extractor, or OCR engine using the respective interfaces. 
        You have full control over the configuration as an RPA developer. 
      

      Fully compatible with the Document Understanding Process Template, which is based on the REFramework. This enables faster development using a standardized, best-practice workflow. 
    

   
      
         Ease of adoption:   Easy to use, available on cloud, no setup required for consuming out-of-the-box models. 
         Can be consumed using the Create Automation option in Document Understanding and Marketplace. 
         Suggested by UiPath&reg; Autopilot <sup> TM </sup> in workflows. 
      

      Seamlessly integrated with Document Understanding modern projects, isolated configuration in a Document Understanding project, enabling reusability. 
      Relying on Document Understanding cloud APIs, leading to quicker bug fixes. 
      Single input/output object, Document Data . 
    

   
      
         Not dependent on a particular technology. 
         Can be consumed from cloud or on-premises environments. 
         Executing without the need of a robot. 
      

  
  
    Drawbacks 
   
      
         Complex configuration, reducing reusability 
         Passing explicit arguments from one activity to the other repeatedly:   Taxonomy 
         Document Object Model 
         Text 
         Classification reults 
         Extraction results 
      

    

    Compared to IntelligentOCR, there are some missing features, which are planned to be added:
      
         Splitting 
         Taxonomy Manager Business Rules 
         Support for multiple extraction methods per document type 
      

   
      
         Requires previous programming experience to be adopted. 
      

  
  
    Use case 
     Use this for complex Document Understanding scenarios that require high flexibility and full control over the extraction pipeline.  
    Use this package if you are just getting started with Document Understanding. Use for new automations relying on:
      
         Modern projects 
         Generative capabilities 
         Out-of-the-box specialized models 
      

     Use API calls to integrate Document Understanding into your applications and systems, including microservices or SaaS architectures.