UiPath-SAIv1 UiPath Certified Professional Specialized AI Professional v1.0 Questions and Answers

In UiPath Communications Mining, the Label Summary report tab provides a high-level overview and statistics on all labels. This summary gives insights into the performance and distribution of labels across the dataset, helping users understand how well the model is classifying different types of communications.

For more details, refer to:

UiPath Communications Mining Documentation: Label Summary Reports

 Entity predictions refer to the process of identifying and highlighting a specific span of text within a communication that represents a value for a predefined entity type. For example, an entity type could be “Organization” and an entity value could be “UiPath”. Entity predictions are made by the platform based on the training data and the rules defined for each entity type. Users can review, accept, reject, or modify the entity predictions using the Classification Station interface12.

References: Communications Mining - Reviewing and applying entities, Communications Mining - Predictions - UiPath Documentation Portal.

In UiPath Communications Mining, the Reports section provides a variety of tools for analyzing and monitoring messages within a dataset. This includes functionalities like label summaries, trends, and message segmentation, which allow users to gain insights into message volumes, sentiment trends, and other analytical metrics. The Reports section is integral for tracking the performance of messages and the overall dataset, making it useful for monitoring communication channels​

In UiPath, the Verbose log level offers the most detailed information about the execution of activities. It logs every possible detail about the automation operations, including variable changes, function calls, and external responses. This level is particularly useful for in-depth debugging and analysis.

UiPath Documentation

The hierarchy of log levels in ascending order of priority is as follows:

Off: No logs are stored.

Verbose: Logs all details about automation operations.

Trace: Logs finer-grained informational events than the Debug level.

Information: Logs informational messages that highlight the progress of the application.

Warning: Logs potentially harmful situations.

Error: Logs error events that might still allow the application to continue running.

Fatal: Logs very severe error events that will presumably lead the application to abort.

Therefore, setting the log level to Verbose ensures that all possible details about the execution are captured, aiding in thorough diagnostics.

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

According to the UiPath Communications Mining documentation, the Trends tab in the Reports page displays charts for verbatim volume, label volume, and sentiment over a selected time period. Users can choose the time period for the data in the filter bar, and the time sequencing of the chart (i.e. daily, weekly, etc.) in the top right dropdown menu. The available options for the time sequencing are Daily, Weekly, Monthly, and Yearly. These options allow users to see how the trends change over different time intervals and identify patterns or anomalies.

References:

Communications Mining - Using Reports

Communications Mining - Trends

In UiPath, the Data Scientist role is primarily responsible for creating, training, and uploading machine learning models to AI Center. While RPA developers might integrate these models into workflows, it is the Data Scientist who builds and fine-tunes models, ensuring their accuracy and relevance for various use cases.

If Label X has 80% precision at a given confidence threshold, this means that out of every 100 messages predicted to have Label X, 80 are correctly labelled, and 20 are incorrectly assigned the label. Precision measures the correctness of predictions made, so in this case, 80% of the predictions were correct, while 20% were false positives​

To automatically retrain and deploy a Document Understanding Machine Learning (ML) Model in AI Center with data from the Document Validation Action, the steps should be followed in this order:

Send Human in the Loop data to the used Dataset.

This step involves sending the data that has been validated and corrected by human reviewers to the dataset. This data will be used for training the ML model.

Use the Export feature from Document Manager using Scheduled Export.

After the data is reviewed and validated, it needs to be exported from the Document Manager. Scheduled Export automates this process, ensuring the dataset in AI Center is regularly updated with new data.

Run Training/Full Pipeline in AI Center using Scheduled Pipeline with Auto-Retraining enabled.

With the updated data in the dataset, the next step is to run the training or the full pipeline. The use of Scheduled Pipeline with Auto-Retraining ensures that the ML model is automatically retrained with the latest data.

Enable the Auto Update feature in the ML Skill.

Finally, enabling the Auto Update feature in the ML Skill ensures that the newly trained model is automatically deployed, making the improved model available for document understanding tasks.

Following these steps in the specified order allows for a streamlined process of continuously improving the ML model based on human-validated data, ensuring better accuracy and efficiency in document understanding tasks over time.

UiPath provides out-of-the-box pre-trained models that are ready for use and cover a wide variety of document types. These models can be used as-is for common use cases or fine-tuned based on specific requirements, making them versatile for different projects

According to the UiPath documentation portal1, the RPA Developer is the role that consumes ML Skills within customized workflows in Studio using the ML Skill activity from the UiPath.MLServices.Activities package. The RPA Developer is responsible for designing, developing, testing, and deploying automation workflows using UiPath Studio and other UiPath products. The RPA Developer can use the ML Skill activity to retrieve and call all ML Skills available on the AI Center service and request them within the automation workflows. The ML Skill activity allows the RPA Developer to pass data to the input of the skill, test the skill, and receive the output of the skill as JSON response, status code, and headers2. Therefore, option C is the correct answer, as it describes the role and the activity that are related to consuming ML Skills in Studio. Option A is incorrect, as the Data Scientist is the role that creates and trains ML models using AI Center or other tools, and publishes them as ML Packages or OS Packages1. Option B is incorrect, as the Administrator is the role that manages the AI Center service, such as configuring the infrastructure, setting up the permissions, and monitoring the usage and performance1. Option D is incorrect, as the Process Controller is the role that deploys ML Packages or OS Packages as ML Skills, and manages the versions, the endpoints, and the API keys of the skills1.

References: 1 AI Center - User Personas 2 Activities - ML Skill

Deep learning is a subset of machine learning that uses multiple layers of artificial neural networks to learn from data and perform complex tasks. The term “deep” refers to the number of layers in the network, which can range from a few to hundreds or even thousands. Each layer consists of a set of nodes that perform mathematical operations on the input data and pass the output to the next layer. The network learns by adjusting the weights of the connections between the nodes based on the feedback from the desired output. Deep learning can handle various types of data, such as images, text, speech, or video, and can automatically extract features and patterns from them without human intervention. Deep learning is behind many applications of artificial intelligence, such as computer vision, natural language processing, speech recognition, and generative models123.

References: 1: What is Deep Learning? | IBM 2: What Is Deep Learning? Definition, Examples, and Careers | Coursera 3: Deep learning - Wikipedia

To iterate through all Microsoft Word documents in a local folder using the For Each File in Folder activity, you should use the filter option "*.doc*". This filter utilizes the asterisk (*) wildcard to match any number of characters, effectively capturing both .doc and .docx file extensions.

UiPath Documentation

In the Filter by field of the activity, entering "*.doc*" ensures that the iteration includes all files with names ending in .doc or .docx, which are standard extensions for Microsoft Word documents.

Other options are incorrect because:

B. Microsoft Word: This is not a valid filter pattern.

*C. " doc"**: This pattern looks for files with names ending in " doc" and does not account for file extensions.

*D. " doc, *docx"**: This is not a valid filter pattern; multiple patterns should be separated by semicolons (e.g., "*.doc;*.docx").

Therefore, the correct filter to use is "*.doc*".

 The Config file in the UiPath Document Understanding Template is a JSON file that contains various parameters and values that control the behavior and functionality of the template. One of the purposes of the Config file is to store the API keys and authentication credentials for accessing external services, such as the Document Understanding API, the Computer Vision API, the Form Recognizer API, and the Text Analysis API. These services are used by the template to perform document classification, data extraction, and data validation tasks. The Config file also allows the user to customize the template according to their needs, such as enabling or disabling human-in-the-loop validation, setting the retry mechanism, defining the custom success logic, and specifying the taxonomy of document types.

References: Document Understanding Process: Studio Template, Automation Suite - Document Understanding configuration file

The Present Classification Station activity is used for classification validation in attended mode. It allows the user to review and correct the classification results of documents using the Classification Station interface. The other options are not suitable for attended mode, as they are either used for creating Action Center tasks (A and C) or for training classifiers (B).

References: Classification Station - UiPath Documentation Portal, Document Classification Validation Overview - UiPath Documentation Portal.

In UiPath's Document Understanding Framework, UiPath Document OCR is recommended as the initial OCR engine for processing documents. This OCR option is optimized for extracting text from a wide variety of document types and provides good accuracy with structured, semi-structured, and unstructured documents. It is designed to work seamlessly within the UiPath Document Understanding process and is highly compatible with other UiPath activities and models, making it a preferred choice for starting document processing in most projects.

For more details, refer to:

UiPath Document Understanding Framework: UiPath OCR Engines

UiPath Document OCR: UiPath OCR Guide

 Entities are additional elements of structured data which can be extracted from within the verbatims. Entities include data such as monetary quantities, dates, currency codes, organisations, people, email addresses, URLs, as well as many other industry specific categories. Entities represent concepts, themes, and intents that are relevant to the business use case and can be used for filtering, searching, and analyzing the verbatims.

References:

Communications Mining - Entities

Communications Mining - Using Entities in your Application

Communications Mining - Configuring Entities

UiPath Studio does not allow connecting to multiple source control plugins at the same time. A single version control system (e.g., GIT, TFS, SVN) can be used per project to manage code versions.

According to the UiPath documentation portal1, the Document Understanding Process is a fully functional UiPath Studio project template based on a document processing flowchart. It provides logging, exception handling, retry mechanisms, and all the methods that should be used in a Document Understanding workflow, out of the box. The Document Understanding Process is preconfigured with a series of basic document types in a taxonomy, a classifier configured to distinguish between these classes, and extractors to showcase how to use the Data Extraction capabilities of the framework. It is meant to be used as a best practice example that can be adapted to your needs while displaying how to configure each of its components1. The Document Understanding Framework, on the other hand, is a set of activities that can be used to build custom document processing workflows. The framework facilitates the processing of incoming files, from file digitization to extracted data validation, all in an open, extensible, and versatile environment. The framework enables you to combine different approaches to extract information from multiple document types. The framework consists of several components, such as Taxonomy, Digitization, Classification, Data Extraction, Data Validation, and Data Consumption2. Therefore, option D is the correct answer, as it describes the difference between the Document Understanding Process and the Document Understanding Framework.

References: 1 Document Understanding Process: Studio Template 2 Document Understanding - Introduction

 The exported data from the UiPath Document Understanding Template contains the extraction results in a JSON format, along with some additional information that can be useful for debugging or analysis purposes. One of the additional information that can be included is the page number from which the field was extracted and the exact position on the page, represented by the coordinates of the bounding box. This information can help to locate the field on the original document image and to verify the accuracy of the extraction. The additional information can be enabled or disabled by setting the IncludeMetadata parameter to true or false in the Config file of the template.

References: Document Understanding Process: Studio Template, Export Results

UiPath AI Center offers three primary package types: pre-trained, custom training, and fine-tunable models. These are essential for various use cases, from leveraging existing models to training custom ones based on specific data

The Document Understanding Process is a fully functional UiPath Studio project template based on a document processing flowchart. It supports both attended and unattended robots with human-in-the-loop validation via Action Center. The process uses queues to store and process the input files, one file per queue item. However, the Auto Retry Functionality should be disabled on queues, because it can interfere with the human validation step and cause errors or duplicates. The process handles the retry mechanisms internally, using the Try/Catch and Error management features.

References:

Document Understanding Process: Studio Template

Document Understanding Process - New Studio Template

In the UiPath Document Understanding Framework, the Train stage enables models to learn from human-validated data. This process involves feeding the corrections made by humans during the validation phase back into the model, allowing it to refine its predictions and improve accuracy over time.

UiPath Documentation

The training component is crucial for classifiers and extractors capable of learning from human feedback. By incorporating validated data, these components can adjust their algorithms to better handle similar documents in the future, enhancing the overall efficiency and effectiveness of the automation process.

Other options are incorrect because:

B. Allows the extractor to improve its prediction over time by using better OCR engines: While better OCR engines can enhance data extraction, this is not the function of the Train stage.

C. Allows a human to validate and correct the extracted data: This describes the Validation stage, not the Train stage.

D. Improves the extractor accuracy by learning from the classification result: Training focuses on learning from human-validated extraction results, not just classification outcomes.

Therefore, the primary purpose of the Train stage is to allow the model to learn from human-validated data, thereby improving its future performance.

When uploading an ML package in UiPath AI Center with the Enable Training option inactive, several validation checks are performed:

There must be a non-empty root folder.

A requirements.txt file must be present to define dependencies.

A main.py file should be in the root folder, which implements a class Main.

The class must implement the necessary methods, such as __init__ and predict.

For more details, refer to:

UiPath AI Center Documentation: ML Package Validation

When creating an AI Center project in UiPath, the fields available to input are the project's name and description. These fields allow you to clearly label and describe the purpose of the AI project within the UiPath platform. Permissions and labels can be managed separately after the project is created​

In this scenario, the rules defined in the Taxonomy Manager are as follows:

IsNotEmpty: Ensures that the field is not empty.

EndsWithUSA: Checks if the extracted address ends with "USA".

ContainsNY: Ensures that the extracted address contains "NY".

The address extracted in this case is: "42 W 80th St. West New York, NJ 1234, USA". While the address ends with "USA" (passing the EndsWithUSA rule), it includes "West New York, NJ", which satisfies the ContainsNY rule even though "NY" is part of "New York". However, the exact behavior of the Contains rule can generate a warning message because "NY" is part of a larger string ("New York"). Since this does not constitute an error but simply a rule conflict, the validation can proceed.

Therefore, the most accurate outcome would be a warning, but validation can still be performed

Mining, it is recommended that users provide a minimum of 25 pinned examples per label to ensure proper training and accurate predictions by the machine learning models. This number allows the platform to have a sufficient variety of examples to generalize and make reliable predictions for each label in real-world scenarios.

The minimum number of pinned examples per label is crucial because it enhances both precision and recall, helping the model effectively differentiate between labels and improving overall model performance. If fewer examples are provided, the model may struggle with generalization and might not perform well in distinguishing between similar or overlapping categories.

This standard of 25 pinned examples is outlined in several UiPath documentation sections and best practices for training models in Communications Mining​

UiPath Documentation

​

UiPath Documentation

​

UiPath Community Forum

For further details, refer to UiPath’s official Communications Mining User Guide on their documentation portal.

In UiPath's AI Center, a Pipeline can be scheduled for execution either at a specific future date or with a recurring schedule. This allows for flexibility in automating the retraining or execution of machine learning models based on predefined time intervals or specific dates. For example, you can schedule a pipeline to run once on a given date or set it to run daily, weekly, or monthly, depending on the project's needs.

For more information, refer to:

UiPath AI Center Documentation: Pipeline Scheduling

Automation Pipelines in AI Center: Pipeline Execution and Scheduling

A high-level view of the tabs within an AI Center project is as follows:

Dashboard: This tab provides an overview of the project’s status, such as the number of datasets, pipelines, packages, skills, and logs, as well as the AI Units consumption and quota.

Datasets: This tab enables you to upload, view, and manage the datasets that are used for training and evaluating the ML models within the project. A dataset is a folder of storage containing arbitrary files and sub-folders1.

Data Labeling: This tab enables you to upload raw data, annotate text data in the labeling tool (for classification or entity recognition), and use the labeled data to train ML models. It is also used by the human reviewer to re-label incorrect predictions as part of the feedback process2.

ML Packages: This tab enables you to upload, view, and manage the ML packages and package versions within the project. An ML package is a group of package versions of the same package type, and a package version is a trained model that can be deployed to a skill3.

Pipelines: This tab enables you to create, view, and manage the pipelines and pipeline runs within the project. A pipeline is a description of an ML workflow, including the functions and their order of execution, and a pipeline run is an execution of a pipeline based on code provided by the user4.

ML Skills: This tab enables you to deploy, view, and manage the ML skills within the project. An ML skill is a live deployment of a package version, which can be consumed by an RPA workflow using an ML skill activity in UiPath Studio5.

ML Logs: This tab enables you to view and filter the logs related to the project, such as the events, messages, and errors that occurred during the pipeline runs, skill deployments, and skill executions6.

References:

1: About Datasets 2: About Data Labeling 3: About ML Packages 4: About Pipelines 5: About ML Skills 6: About ML Logs

 According to the UiPath documentation, UiPath Communications Mining is a tool that enables you to analyze text-based communications data, such as customer feedback, support tickets, or chat transcripts, using natural language processing (NLP) and machine learning (ML) techniques1. One of the features of UiPath Communications Mining is the Comparison page, which allows you to compare two cohorts of verbatims based on different criteria, such as date range, source, metadata, or label2. The Comparison page displays the following information for each cohort3:

Total verbatim count: The number of verbatims in the cohort.

Proportion for each label: The percentage of verbatims in the cohort that are assigned to each label. A label is a category or a topic that is relevant for the analysis, such as sentiment, intent, or issue type. Labels can be predefined or custom-defined by the user.

Statistical significance: The p-value that indicates whether the difference in proportions between the two cohorts is statistically significant or not. A p-value less than 0.05 means that the difference is unlikely to be due to chance.

The Comparison page also provides a visual representation of the proportions for each label using a bar chart, and allows the user to drill down into the verbatim content for each label by clicking on the bars3. Therefore, the correct answer is A.

References:

1: About Communications Mining 2: Communications Mining - Comparing Cohorts 3: Communications Mining - Comparison Page

Making an ML Skill public in UiPath enables it to be accessed externally from the UiPath ecosystem. This can be beneficial if the ML Skill needs to be utilized in external applications, systems, or services beyond UiPath's automation environment. Public access expands the usability of the skill, allowing integration with other systems while maintaining security through managed endpoints.

The Configure Extractors Wizard is a tool that enables you to select and customize the extractors that are used for data extraction from documents. It is accessed via the Data Extraction Scope activity, which is a container for extractor activities. The wizard allows you to map the fields defined in your taxonomy with the fields supported by each extractor, and to set the minimum confidence level and the framework alias for each extractor. The wizard is mandatory for the extractor configuration, as it ensures that the extractors are applied correctly to each document type and field1.

References: Configure Extractors Wizard of Data Extraction Scope

UiPath AI Center can be deployed in multiple ways to meet different organizational needs and infrastructures. The available deployment options include:

Cloud availability: Using UiPath's cloud services.

On-premises air-gapped: A fully isolated, offline environment for organizations with strict security requirements.

On-premises online: Deployed on-premise but with internet connectivity.

Hybrid mode: Combining on-premises AI Center with on-premises Orchestrator for flexibility.

Automation Suite: A comprehensive deployment of UiPath tools, including AI Center.

For more details, refer to:

UiPath AI Center Deployment Models: Deployment Options

 A label taxonomy is a hierarchical structure of concepts that you want to capture from your communications data, such as emails, chats, or calls. Each label represents a specific concept that serves a business purpose and is aligned to your objectives. A label taxonomy can have multiple levels of hierarchy, where each child label is a subset of its parent label. For example, a parent label could be “Product Feedback” and a child label could be “Product Feature Request” or “Product Bug Report”. A label taxonomy is used to train a machine learning model that can automatically classify your communications data according to the labels you defined1.

One of the best practices for designing a label taxonomy is to ensure that each label is clearly identifiable from the text of the individual verbatim (not thread) to which it will be applied. A verbatim is a single unit of communication, such as an email message, a chat message, or a call transcript segment. A thread is a collection of related verbatims, such as an email conversation, a chat session, or a call recording. When you train your model, you will apply labels to verbatims, not threads, so it is important that each label can be recognized from the verbatim text alone, without relying on the context of the thread. This will help the model to learn the patterns and features of each label and to generalize to new data. It will also help you to maintain consistency and accuracy when labelling your data2.

References: 1: Communications Mining - Taxonomies 2: Communications Mining - Label hierarchy and best practice

According to the UiPath documentation, the field name for a column field in Document Manager does not accept uppercase letters. It can only contain lowercase letters, numbers, underscore _ and dash -12. Therefore, the only option that meets these criteria is D. First_name123. The other options are invalid because they either contain uppercase letters, spaces, or @ symbols, which are not allowed.

References: 1: Document Understanding - Create and Configure Fields 2: Document Understanding - Create & Configure Fields

In UiPath Document Manager, for string fields, the available options for scoring include:

Exact match: This checks whether the extracted string exactly matches the expected value.

Levenshtein: This method computes the "distance" between two strings, which is the number of single-character edits (insertions, deletions, or substitutions) required to change one string into the other. It is used to assess the similarity between the extracted string and the expected value.

These scoring methods help evaluate the accuracy of string extraction in the document understanding process.

For more details, refer to:

UiPath Document Understanding Framework: String Field Scoring

Levenshtein Distance in UiPath: Scoring String Fields

In UiPath AI Center, versioning of ML packages is an integral part of managing the lifecycle of machine learning models. Each ML package has a major and minor version to track changes. When an ML package is initially uploaded, it is assigned a major version (e.g., 1.0). If a package is retrained via pipelines, it increments the minor version (e.g., from 1.0 to 1.1). This mechanism helps differentiate between user-uploaded packages and those that have been retrained. Only packages that undergo retraining through pipelines modify their minor version, not the major version. Thus, answer D is correct.

(Source: docs.uipath.com on ML Package Management).

The correct pipeline configuration for creating a new model version that includes both the initial 1000 pages and the newly labeled 800 pages is to run a Full pipeline. This ensures that the model is fully retrained with all available data (1800 pages in total). The evaluation dataset should remain the 100 pages to gauge the model's performance after retraining. This approach maximizes the model's learning by incorporating all labeled data while allowing for evaluation against a known dataset.

According to the UiPath documentation, OmniPaqe is a paid OCR engine that requires a license to use. It is one of the most accurate and reliable OCR engines available, and it supports over 200 languages. The other OCR engines listed are free of charge, but they may have different features, limitations, and performance levels. For example, Tesseract is an open-source OCR engine that supports over 100 languages, but it may not be as accurate as OmniPaqe. Microsoft Azure OCR and Microsoft OCR are both cloud-based OCR engines that use Microsoft’s technology, but they have different capabilities and pricing models. Microsoft Azure OCR can process both printed and handwritten text, and it uses a pay-as-you-go model based on the number of transactions. Microsoft OCR can only process printed text, and it is included in the UiPath Studio license.

References:

Document Understanding - OCR Engines

Automation Pricing - Complete UiPath Enterprise Solution

According to the UiPath documentation portal1, the Automation Suite installer is a single package that enables the deployment of the full UiPath Automation Platform in the environment of choice, whether on-premises or in the cloud. The Automation Suite installer contains all the components and dependencies required for the installation, such as the infrastructure, the orchestrator, the AI Center, the Action Center, the Insights, the Test Suite, and the Document Understanding. The Automation Suite installer also supports multi-node deployment with automatic scaling and built-in high availability, as well as easy monitoring, configuration, and upgrade options1. Therefore, option C is the correct answer, as it describes the features and benefits of the Automation Suite installer. Option A is incorrect, as it refers to the UiPath Automation Cloud, which is a different offering that does not require an installer. Option B is incorrect, as it describes a manual installation process that is not enabled by the Automation Suite installer. Option D is incorrect, as it confuses the Automation Suite installer with the installUiPathAS.sh script, which is a separate file that is used to launch the installer wizard2.

References: 1 Automation Suite - Overview 2 Automation Suite - Downloading the installation packages

Here is the correct order to configure the Extractor Wizard in UiPath Document Understanding:

Step 1: Add a Data Extraction Scope activity to the workflow.Step 2: Place one or more extractors.Step 3: Click on the Configure Extractors button.Step 4: Select the checkboxes next to each field for the extractor type that should be activated.Step 5: Get capabilities (if needed).Step 6: Click on the Save button.

This sequence ensures that the Extractor Wizard is correctly configured to work with the Document Understanding workflow.

To enable the Taxonomy Manager button in the Ribbon, the UiPath.IntelligentOCR.Activities package must be installed. This package includes all activities related to Document Understanding, including the Taxonomy Manager.

The Custom Named Entity Recognition out-of-the-box model is a machine learning package that allows you to bring your own dataset tagged with entities you want to extract from unstructured text. The model can be trained and deployed using the UiPath AI Center, and can be integrated with the UiPath Document Understanding framework. The model can be used to extract and classify text in various domains and formats, such as emails, letters, web pages, research papers, and call transcripts. For example, you can use the model to extract information such as names, dates, addresses, amounts, products, or any other custom entity from your documents. The model supports multiple languages and can be customized according to your needs.

References: AI Center - Custom Named Entity Recognition, Custom Named Entity Recognition Documentation, UiPath AI Center - Document Understanding & Use of UiPath Custom Named Entity Recognition Model

The main purpose of the Document Understanding Process template in UiPath Studio is to provide users with a ready-to-use document processing framework. It is designed to simplify the development of document understanding automations by offering out-of-the-box features like logging, exception handling, and retry mechanisms. This template allows developers to quickly start working on both simple demos and large-scale document processing projects without needing to build everything from scratch. It is equipped with key components such as classifiers and extractors to streamline document classification and data extraction workflows

The Machine Learning Extractor utilizes machine learning models to effectively extract data from documents, especially when dealing with varying structures or formats within the same document type. This capability is crucial in scenarios where documents do not follow a strict template and have variations in their layout or content organization. The extractor can be trained to understand these variations and accurately extract the needed information.

The Machine Learning Extractor is a data extraction tool that uses machine learning models to extract data from various types of documents, such as invoices, receipts, or forms. It is especially useful when the same document type has multiple layouts or formats, as it can learn and infer the values for the targeted fields, even from documents and layouts it has never seen before1.

The Machine Learning Extractor can be used with one of UiPath’s public Document Understanding endpoints, which provide generic models for certain document types, or with custom trained machine learning models hosted in AI Center, which can be tailored to specific use cases. The Machine Learning Extractor can be configured and trained using the Data Extraction Scope activity in UiPath Studio2.

References:

Document Understanding - Machine Learning Extractor

UiPath Activities - Data Extraction Scope

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.

References:

AI Center - AI Units

Document Understanding - Metering & Charging Logic

 According to the UiPath Document Understanding Process template, the best way to test the code in a development or testing environment is to create test data based on the use case developed, and use it to test both the existing and the new tests. The test data should include different document types, formats, and scenarios that reflect the real-world data that the process will handle in production. The existing tests are provided by the template and cover the main functionalities and components of the Document Understanding Process, such as digitization, classification, data extraction, validation, and export. The new tests are created by the developer to test the customizations and integrations that are specific to the use case, such as custom extractors, classifiers, or data consumption methods. The test data and the test cases should be updated and maintained throughout the development lifecycle to ensure the quality and reliability of the code.

References:

Document Understanding Process: Studio Template

Document Understanding Process: User Guide

The End Process is the final stage of the Document Understanding Process, which is a fully functional UiPath Studio project template based on a document processing flowchart. The End Process is responsible for setting the queue transaction status, logging the results, and performing any post processing or cleaning actions if needed. The End Process sets the queue transaction status as Successful if the document was processed without any exception, and as Failed if an exception occurred, either a Business Exception (such as invalid data) or a System Exception (such as network failure). The End Process also adds the extracted data and the validation status as output arguments to the queue transaction. The End Process also logs the processing statistics, such as the number of documents processed, the number of exceptions, the average processing time, and the accuracy rate. The End Process also performs any post processing or cleaning actions, such as deleting temporary files, closing applications, or sending notifications1.

References: 1: Document Understanding Process: Studio Template