When setting up a classification label in UiPath's Out Of the Box (OOB) labeling templates, you need to provide several key details: the name of the label, the classification type (which defines the kind of label), the input to be labeled, the attribute name that describes the label's context, a shortcut for quick access, and a color for visual distinction. These fields ensure the label is fully defined and easy to manage in workflows.

(Source: UiPath Document Understanding documentation)

According to the UiPath documentation, a UiPath Communications Mining taxonomy is a collection of all the labels applied to the verbatims in a dataset, structured in a hierarchical manner. Labels are the concepts and intents that you want to capture in the dataset to suit your specific objectives. When you import your taxonomy from a spreadsheet, you need to provide the label descriptions, which are the names of the labels and their level in the hierarchy. Label predictions and entity predictions are the outputs of the model training process, and they are not part of the taxonomy. Entity descriptions are the definitions of the entities that you want to extract from the verbatims, and they are not part of the taxonomy either.

The DocumentUnderstanding ML package is a generic, retrainable model designed to handle various document types that are not covered by out-of-the-box models. It allows for the extraction of data from structured and semi-structured documents by building a model from scratch through training. This package is highly flexible and can be tailored to fit different document formats, making it ideal when specific document types are not pre-configured in UiPath’s out-of-the-box offerings.(Source: UiPath Documentation on ML Packages

 The ML Extractor is a data extraction tool that uses machine learning models provided by UiPath to identify and extract data from documents. The ML Extractor can work with predefined document types, such as invoices, receipts, purchase orders, and utility bills, or with custom document types that are trained using the Data Manager and the Machine Learning Classifier Trainer12.

According to the best practice, the ML Extractor should be chosen based on the document types, language, and data quality of the documents being processed. It is important to select an ML Extractor that is specifically trained or optimized for the document types that are relevant for the use case, as different document types may have different layouts, fields, and formats. It is also important to take into account the language of the documents, as some ML Extractors may support only certain languages or require specific language settings. Moreover, it is important to consider the quality and diversity of the training data used to train the ML Extractor, as this may affect the accuracy and reliability of the extraction results. The training data should be representative of the real-world data, and should cover various scenarios, variations, and exceptions3.

The RegEx Based Extractor is most effective for documents where data fields follow a strict and predictable format, such as dates, invoice numbers, or specific patterns like email addresses. This method is well-suited for extracting information from structured or semi-structured documents with consistent formats across different documents, making it highly reliable for use cases where patterns are easily identifiable and do not vary significantly.

(Source: UiPath Document Understanding documentation)

UiPath Communications Mining uses Natural Language Processing (NLP) to analyze and process unstructured communication data such as emails, chat logs, and other textual inputs. This enables automation to identify actionable insights from large volumes of communication data.

According to the UiPath documentation, Page Units are the measure used to license Document Understanding products. Page Units are charged based on the number of pages processed by the Document Understanding models, such as extractors, OCR engines, and classifiers. Therefore, applying OCR on a 10-page document consumes Page Units, while the other options do not. The creation of a Document Validation Action in Action Center does not consume any Page Units, as it is a human-in-the-loop activity. Using ML Classifier on a 21-page document does not consume Page Units, as it is a free model. Using Intelligent Form Extractor on a 5-page document with 0 successful extractions does not consume Page Units, as the extractor only charges for successful extractions.

Comprehensive and Detailed Explanation From Exact Extract:

The Machine Learning Extractor activity includes a unique property: ML Skill , which references a deployed machine learning model from AI Center . This property allows the extractor to know which model (skill) to call for performing the data extraction.

Other extractors like Regex or Form do not interact with AI Center and thus do not require this property.

UiPath Documentation Reference: Machine Learning Extractor – UiPath Docs

The synchronous API calls for UiPath Document Understanding Cloud are ideal when you need real-time interaction and fast feedback, such as when processing small documents (with up to five pages). This approach is beneficial in use cases requiring low latency, but it is less suitable for large datasets or documents due to limitations in speed and page count