UiPath UiPath-SAIAv1 UiPath Specialized AI Associate Exam (2023.10) Exam Practice Test

Comprehensive and Detailed Explanation From Exact Extract:

Before training a model in Communications Mining, it iscrucial to align the taxonomy and labeling strategy with business goalsto ensure the outputs provide measurable value. This preparation stage helps define KPIs, label definitions, and ensures the AI output leads to actionable automation or insight.

Focusing on value from the startprevents wasted effortand allows prioritization of the most impactful communication types.

UiPath Documentation Reference:Communications Mining – Best Practices for Training

===========

The Label Trends table in UiPath Communications Mining shows the trend of the top 10 highest volume labels over the selected time period, as well as their percentage change and rank change compared to the previous period1. The table allows users to quickly identify which labels are increasing or decreasing in volume, and by how much, over time. The table also shows the net sentiment score for each label, which is calculated as the difference between the positive and negative sentiment probabilities for each verbatim2. The table can be filtered by data type, source, date range, and label category. Users can also sort the table by label name, volume, percentage change, rank change, or net sentiment1.

A close-up of a page AI-generated content may be incorrect.

to load a taxonomy from a given non-default location text file into a variable, the order of steps should be as follows:

Create a new variable of type 'DocumentTaxonomy' called 'documentTaxonomy', then create a new string variable called 'taxonomyPath'.

This step involves setting up the necessary variables that will be used in the process. The 'documentTaxonomy' variable will hold the deserialized taxonomy object, and 'taxonomyPath' will store the path to the taxonomy file.

Using an Assign activity, assign the given non-default taxonomy text file path to the most recent variable created.

Here you will assign the path of the taxonomy file to the 'taxonomyPath' variable.

Use the Read Text File activity on the 'taxonomyPath' variable created. Next, create a new variable 'taxonomyText', then save the output of the Read Text File activity to 'taxonomyText'.

This step is where you read the contents of the taxonomy file using the 'Read Text File' activity. The contents are stored in the 'taxonomyText' variable.

Inside the last Assign activity 'Value to Save' property add the following expression: "Newtonsoft.Json.JsonConvert.DeserializeObject(Of DocumentTaxonomy)(taxonomyText)" where 'taxonomyText' is the text read from the file and 'documentTaxonomy' (the most recent variable created) is the variable you created.

In this final step, you will deserialize the JSON content from the 'taxonomyText' into a 'DocumentTaxonomy' object using the 'JsonConvert.DeserializeObject' method and assign it to the 'documentTaxonomy' variable.

Following these steps in this order will load the taxonomy from a text file into the 'documentTaxonomy' variable in UiPath.

 The Reports section of the dataset navigation bar in UiPath Communication Mining allows users to access detailed, quervable charts, statistics, and customizable dashboards that provide valuable insights and analysis on their communications data1. The Reports section has up to six tabs,depending on the data type, each designed to address different reporting needs2:

Dashboard: Users can create custom dashboard views using data from other tabs, such as label summary, trends, segments, threads, and comparison. Dashboards are specific to the dataset and can be edited, deleted, or renamed by users with the ‘Modify datasets’ permission3.

Label Summary: Users can view high-level summary statistics for labels, such as volume, precision, recall, and sentiment. Users can also filter by data type, source, date range, and label category.

Trends: Users can view charts for verbatim volume, label volume, and sentiment over a selected time period. Users can also filter by data type, source, date range, and label category.

Segments: Users can view charts comparing label volumes to verbatim metadata fields, such as sender domain, channel, or language. Users can also filter by data type, source, date range, and label category.

Threads: Users can view charts of thread volumes and label volumes within a thread, if the data is in thread form, such as call transcripts or email chains. Users can also filter by data type, source, date range, and label category.

Comparison: Users can compare different cohorts of data against each other, such as different sources, time periods, or label categories. Users can also filter by data type, source, date range, and label category.

According to UiPath documentation, model versions can be pinned and managed on the "models" tab, ensuring that users can maintain and revert to specific versions when necessary for continuity and performance

The environment variable eval.redo_ocr is relevant for Evaluation pipelines because it allows you to rerun OCR when running the pipeline to assess the impact of OCR on extraction accuracy. This assumes an OCR engine was configured when the ML Package was created. The other options are not valid environment variables for Evaluation pipelines.

Model-based data extraction, often involving machine learning models, is particularly effective for handling complex data structures such as variable-length data or data that spans multiple pages.This approach adapts better to varying formats and can extract information more accurately in such scenarios compared to rule-based or manual methods.

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:

If a Try Catch activity has no defined Catch blocks and the Try section throws an exception, the exception is not caught and will propagate, potentially terminating the workflow.

However, if no exception occurs, the process continues normally.

The activity does not result in validation errors just because Catch blocks are empty.

UiPath Documentation Reference:

Try Catch Activity – UiPath Docs

===========

According to the UiPath documentation and web search results, OCR (Optical Character Recognition) is a method that reads text from images, recognizing each character and its position. OCR is used to digitize documents and make them searchable and editable. OCR can be performed by different engines, such as Tesseract, Microsoft OCR, Microsoft Azure OCR, OmniPaqe, and Abbyy. OCR is a basic step in the Document Understanding Framework, which is a set of activities and services that enable the automation of document processing workflows.

IntelligentOCR is a UiPath Studio activity package that contains all the activities needed to enable information extraction from documents. Information extraction is the process of identifying and extracting relevant data from documents, such as fields, tables, entities, and labels. IntelligentOCR uses different components, such as classifiers, extractors, validators, and trainers, to perform information extraction. IntelligentOCR also supports different formats, such as PDF, PNG, JPG, TIFF, and BMP. IntelligentOCR is an advanced step in the Document Understanding Framework, which builds on the OCR output and provides more functionality and flexibility.

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 Document Understanding Cloud APIs, the Generative Classifier is used to classify documents by leveraging a generative AI model. To classify a document as either an "Invoice" or a "Receipt," a POST request must be sent to the /api/framework/projects/{projectId}/classifiers/generative_classifier/classification endpoint. The body of this request should contain prompts specifying the classification types (in this case, "Invoice" and "Receipt") along with their corresponding descriptions. This allows the model to correctly classify incoming documents based on these predefined prompts.

For further reading, refer to:

UiPath Document Understanding API Documentation: Cloud API for Classification

Generative Classifier APIs: UiPath Classification APIs

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

Comprehensive and Detailed Explanation From Exact Extract:

UiPath allows developers to buildcustom extractorsthat can be used within theData Extraction Scopeactivity by implementing a specific interface. This is done by referencing theUiPath.DocumentProcessing.Contractsassembly in the custom extractor.

This enables plugging custom ML models or logic into the Document Understanding workflow.

Custom extractors must implement interfaces like IExtractor or IFormExtractor.

UiPath Documentation Reference:Create a Custom Extractor – UiPath Docs

===========

According to the UiPath documentation, the recommended number of documents per vendor to train the initial dataset is 10. This means that for each vendor that provides a specific type of document, such as invoices or receipts, you should have at least 10 samples of their documents in your training dataset. This helps to ensure that the dataset is balanced and representative of the real-world data, and that the machine learning model can learn from the variations and features of each vendor’s documents. Having too few documents per vendor can lead to poor model performance and accuracy, while having too many documents from a single vendor can cause overfitting and bias1.

When creating an ML Package in UiPath AI Center, the package name must adhere to Python naming conventions, meaning it cannot include reserved keywords such as class, break, finally, etc. This ensures that the package can be successfully deployed without conflicts in the Python environment.

Unstructured documents are those that do not have a predefined format or layout, and therefore cannot be easily processed by traditional methods. They often contain free-form text, images,tables, and other elements that vary from document to document. Examples of unstructured documents include contracts, agreements, emails, letters, reports, articles, and so on. UiPath Document Understanding is a solution that enables the processing of unstructured documents using AI-powered models and RPA workflows1.

The other options are not correct because they are examples of structured or semi-structured documents. Structured documents are those that have a fixed format or layout, and can be easily processed by rules-based methods. They often contain fields, labels, and values that are consistent across documents. Examples of structured documents include banking forms, tax forms, surveys, identity cards, and so on. Semi-structured documents are those that have some elements of structure, but also contain variations or unstructured content. They often require a combination of rules-based and AI-powered methods to process. Examples of semi-structured documents include invoices, receipts, purchase orders, medical bills, and so on2.

For the described requirements:

ApplyOcrOnPdf set to Auto ensures OCR is applied only when needed.

DegreeOfParallelism set to -1 uses all available logical processors for maximum parallelism.

Comprehensive and Detailed Explanation From Exact Extract:

Optical Character Recognition (OCR)is a method used to convert different types of documents (PDFs, scanned paper documents, images) intoeditable and searchable databy recognizing characters and their positions.

OCR is vital in Document Understanding todigitize unstructured data from images and scanned docs.

UiPath Documentation Reference:OCR Engines in Document Understanding

===========

As a best practice, Subject Matter Experts (SMEs) should perform the data labeling in UiPath Communications Mining or Document Understanding projects. SMEs have the in-depth knowledge of the specific content and context, which ensures that the data is labeled correctly andmeaningfully for training machine learning models. Their expertise is essential for accurate taxonomy and data preparation

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.

Comprehensive and Detailed Explanation From Exact Extract:

ML models arebest suited for complex, semi-structured or unstructured documentswhere rules or templates can't handle layout variability. For example, invoices from many vendors with different formats are ideal for ML.

In contrast, fixed-format documents are better handled with regex, form, or template-based extractors.

UiPath Documentation Reference:Choosing the Right Extractor – Document Understanding

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

According to the UiPath documentation, the available options for Scoring in Document Manager, that apply only to string content type, are exact match and Levenshtein. Exact match is a scoring strategy that considers a prediction to be correct only if it exactly matches the true value. Levenshtein is a scoring strategy that measures the similarity between two strings by counting the minimum number of edits (insertions, deletions, or substitutions) required to transform one string into another. The lower the Levenshtein distance, the higher the score. These options can be configured in the Advanced tab of the Edit Field window for string fields.

Comprehensive and Detailed Explanation From Exact Extract:

Processes that undergofrequent business logic changesrequire frequent updates to automation scripts, resulting inhigh maintenance effortand potential breakdowns in unattended execution.

Stable, rules-based processes are preferred for long-term, low-maintenance automation.

UiPath Academy Reference:RPA Developer Foundation – “Process Assessment and Selection” Module

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.

 The ML Classifier is a document classifier that uses a machine learning model deployed as an ML Skill in AI Center to perform document classification tasks. The ML Classifier can work by default with Invoices, Purchase Orders, Receipts, 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 Classifier is the only recommended classifier to be used when the custom document types are very similar and file splitting is not necessary. This is because the ML Classifier can handle complex and ambiguous cases where the document types are hard to distinguish by rules or keywords, and can also learn from feedback and improve over time. File splitting is not necessary when the documents are single-page or have a consistent number of pages per document type3.

The other options are not correct because they are scenarios where other classifiers, such as the Keyword Based Classifier or the Intelligent Keyword Classifier, can be used in combination with the ML Classifier or instead of it. These classifiers are based on rules or keywords that can identify the document types based on their content or metadata, and can also perform file splitting if the documents are multi-page or have a variable number of pages per document type3.

The Shuffle training mode in the "Explore" phase of UiPath Communications Mining helps to introduce randomness into the training data. This prevents labeling bias by ensuring that the model does not overly focus on certain labels or examples, leading to a more balanced and generalized model. By shuffling the data, the model is exposed to a diverse range of examples, which enhances its ability to make accurate predictions across different labels and datasets.

(Source: UiPath Communications Mining documentation)

A screenshot of a computer AI-generated content may be incorrect.

Export the package from AI Center. This is the first step where you prepare the package to be moved.

On the ML Packages page, click the Import ML Package button. This step is where you start the process of importing the package you've exported.

On the Upload package field, add the zip file downloaded using the Downloading ML Packages procedure. After starting the import process, you will upload the actual package.

Click Create. This is the final step where you finalize the uploading process of your ML package.

Please proceed with these steps in the UiPath AI Center to upload your exported package correctly.

The Data Extraction Scope activity provides a scope for extractor activities, enabling you to configure them according to the document types defined in your taxonomy. The output of the activity is stored in an ExtractionResult variable, containing all automatically extracted data, and can be used as input for the Export Extraction Results activity. This activity also features a Configure Extractors wizard, which lets you specify exactly what fields from the document types defined in the taxonomy you want to extract1.

The extractors that can be used for Data Extraction Scope activity are:

Regex Based Extractor: This extractor enables you to use regular expressions to extract data from text documents. You can define your own expressions or use the predefined ones from the Regex Based Extractor Configuration wizard2.

Form Extractor: This extractor enables you to extract data from semi-structured documents, such as invoices, receipts, or purchase orders, based on the position and relative distance of the fields. You can define the templates for each document type using the Form Extractor Configuration wizard3.

Intelligent Form Extractor: This extractor enables you to extract data from semi-structured documents, such as invoices, receipts, or purchase orders, based on the labels and values of the fields. You can define the fields for each document type using the Intelligent Form Extractor Configuration wizard.

Machine Learning Extractor: This extractor enables you to extract data from any type of document, using a machine learning model that is trained on your data. You can use the predefined models from UiPath or your own custom models hosted on AI Center or other platforms. You can configure the fields and the model for each document type using the Machine Learning ExtractorConfiguration wizard.

The Images folder in the exported dataset from UiPath's Document Manager contains each page of the documents in the dataset saved as images. This ensures that the visual layout of the documents is preserved, which is especially important when working with scanned documents or files that need to retain their original format for processing or validation purposes​

When migrating a schema from Document Manager to a Modern Project, UiPath will override any existing schema associated with the document type if you attempt to import a new schema. This behavior is confirmed in UiPath's handling of document types and schema imports, where the new schema will replace the old one, ensuring that the latest version is applied to the project. This helps maintain consistency in schema configurations during migrations, especially when schemas are updated or need to be standardized

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.

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.

 Document Understanding is a tool that helps you create and manage documents for your automation scenarios in the UiPath ecosystem. It allows you to process and extract data from multiple document types in an open, extensible, and versatile environment. The framework consists of components such as Taxonomy, Digitization, Data Extraction, Data Extraction Validation, Data Extraction Training, and Data Consumption, and enables you to customize and train your own algorithms12.

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.

It is essential to analyze the languages involved in a project because different components of UiPath's Document Understanding framework have varying language support. For instance, some OCR engines and classifiers support specific languages, and this determines whether a particular language can be processed accurately. As the supported languages differ across components such as the Machine Learning Extractor, Form Extractor, and various OCR services, selecting the right components is crucial to meeting project requirements​

Comprehensive and Detailed Explanation From Exact Extract:

TheMachine Learning Extractoris best suited for handlingsemi-structured documentslike invoices, which often vary by layout, format, and provider. Unlike template-based extractors, ML extractors learn from data and generalize across multiple formats.

It is trained to recognize fields regardless of positioning or formatting, making it ideal for vendor invoices, receipts, and more.

UiPath Documentation Reference:Choosing the Right Extractor – UiPath DU

===========

In UiPath Communications Mining, high coverage ensures that a larger proportion of communications is classified with meaningful labels, meaning fewer communications are sent for manual review and more processes are captured for automation. This leads to more effective automation, reducing the need for human intervention and ensuring that the automation use case is fully realized.

For more details, refer to:

UiPath Communications Mining Performance Metrics: Coverage and Automation

From the provided workflow:

The Assign Status activity sets the variable Status to the value "Approved".

The Check Status activity evaluates the value of Status against defined conditions.

It has branches for "Pending", "New", and "Unknown".

The "Default" branch is triggered if none of these conditions match the value of Status.

Since "Approved" does not match "Pending", "New", or "Unknown", the Default branch will execute.

The Write Line activity in the Default branch outputs "Status not valid." to the Output panel.

Comprehensive and Detailed Explanation From Exact Extract:

ThePresent Classification Stationactivity is specifically used toreview and correct the classification resultsperformed by the "Classify Document" activity.

It allows a human to validate which document type has been assigned before data extraction begins.

UiPath Documentation Reference:Classification Station – Document Understanding

===========

 Data Manager is a web application that allows users to prepare, review, and make corrections to datasets required for Machine Learning models. Data Manager enables users to create and manage datasets, label data, validate and export data, and monitor data quality and progress. Data Manager supports various types of data, such as documents, images, text, and tables. Data Manager is integrated with AI Center, where users can train and deploy Machine Learning models using the datasets created or modified in Data Manager12.

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).

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

To configure the Validation Station as an attended activity in UiPath, the minimum required inputs include the Taxonomy, which defines the structure and fields for data extraction, the Document Path, the Document Object Model (DOM), the Document Text obtained during digitization, and the Automatic Extraction Results, which are the results from automatic data extraction activities that need validation. These inputs allow the Validation Station to properly display and validate extracted data​

Comprehensive and Detailed Explanation From Exact Extract:

One Click Classificationstreamlines the training process by eliminating the need to manually create AI Center components like datasets and pipelines. It enables users totrain custom document classification modelsentirely within the Document Understanding interface in Studio or Orchestrator.

This feature is especially helpful for business users or developers new to AI Center.

UiPath Documentation Reference:One Click Training – Document Understanding

In UiPath Communications Mining, pinning a model ensures that the predictions shown in the Explore tab are generated from that specific model version. This feature allows users to control which version of the model is actively making predictions, particularly during evaluation or comparison stages. By pinning a model, the user ensures that the UI reflects the predictions from the selected version, helping maintain consistency when analyzing results or making changes.

For more details, refer to:

UiPath Communications Mining: Model Management and Pinning

UiPath AI Center Documentation: Managing Model Versions

To ensure the model is trained effectively, UiPath recommends that regular fields be labeled on at least 10 different pages in Data Manager before exporting the labeled documents to AI Center. This helps in providing enough variation and examples for the model to learn from and generalize effectively.

According to the UiPath documentation, the Taxonomy component is used in the Document Understanding Template to define the document types and the fields that are targeted for data extraction for each document type. The Taxonomy component is the metadata that the Document Understanding framework considers in each of its steps, such as document classification and data extraction. The Taxonomy component allows you to create, edit, import, or export the taxonomy of your project, which is a collection of document types and fields that suit your specific objectives. The Taxonomy component also allows you to configure the field types, details, and validations, as well as the supported languages and categories for your documents.

In the context of a machine learning pipeline, specifically within the train.py file in UiPath AI models, the function responsible for persisting the trained model is typically named save(self). This function is invoked after the model has been trained, and it ensures that the model's state, weights, and configurations are saved to disk or another persistent storage medium. The saved model can then be reused for inference or further fine-tuning in future executions.

For more details, refer to:

UiPath AI Center Documentation: Training Models

Model Persistence: Saving Machine Learning Models in AI Center

Comprehensive and Detailed Explanation From Exact Extract:

In UiPath Communications Mining, theDiscoverphase is the initial stage in which the system groups similar messages or conversations based on content. These clusters help users identify patterns and common intents, which serve as a foundation for defininglabels and training taxonomy.

This unsupervised learning approach is essential forbootstrapping model trainingwith minimal manual intervention.

UiPath Documentation Reference:Discover Phase – Communications Mining

 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 theuser 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.

Comprehensive and Detailed Explanation From Exact Extract:

In UiPathIntegration Service, aconnectionis the secure authentication configuration between UiPath and an external application (like Salesforce, ServiceNow, etc.). These connections rely onAPI authentication mechanismssuch as OAuth 2.0 or API Keys depending on the connector.

They are used to enable data exchange between RPA processes and external systems.

UiPath Documentation Reference:Integration Service – Connections

===========

In UiPath AI Center, ML Skills can be managed in various ways, allowing users to customize and control how these skills are deployed and used. The management options include:

Creating a new ML skill.

Stopping a deployed skill.

Redeploying an ML skill.

Updating to a new package version.

Rolling back to a previous version if needed.

Modifying GPU usage.

Modifying the use of AI units.

Making the skill public or private.

Deleting an ML skill when no longer needed.

This provides flexibility for both managing the ML infrastructure and optimizing resources in real-time.

For more details, refer to:

UiPath AI Center Documentation: Managing ML Skills

ML Skill Management Options: Managing Machine Learning Skills in AI Center

In UiPath Communication Mining, the Generative Annotation feature automatically enables Assisted Labelling on datasets. Assisted Labelling helps to accelerate the labeling process by automatically suggesting relevant labels based on the content of the communications. This feature significantly improves the efficiency of the model training process by reducing the manual effort required to label large datasets.

For more details, refer to:

UiPath Communication Mining Documentation: Generative Annotation and Assisted Labelling

Labeling and Annotation in UiPath Communications Mining: UiPath AI Center Documentation

Tone analysis is better suited for monitoring situations like "Quality of Service" in shared mailboxes, where the focus is on evaluating emotional tone in communications that may not always have clear-cut positive or negative sentiments. This contrasts with label sentiment analysis, which is better for datasets with explicit feedback (e.g., customer satisfaction surveys). In operations-focused environments, tone analysis provides more nuanced insights into service quality​

UiPath provides three types of classifier trainers to optimize document classification: Keyword Based Classifier Trainer, Intelligent Keyword Classifier Trainer, and Machine Learning Classifier Trainer. These trainers are used to teach the system how to categorize documents based on keywords, intelligent learning patterns, or machine learning techniques for more complex classifications.(Source: UiPath Classifier Trainer documentation​

his is confirmed in the UiPath documentation, where the "Train" feature guides users from the dataset creation stage through the necessary steps to optimize the training process. The system recommends next best actions based on progress to ensure efficient and focused training​

A screenshot of a computer AI-generated content may be incorrect.

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.

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)

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​

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.

An ML skill is a consumer-ready, live deployment of an ML or OS package that can be used in RPA workflows. By default, an ML skill is private, which means it can only be accessed by the users who have the permission to view and manage the project that contains the skill. However, an ML skill can be made public by enabling the Public Skill option in the ML Skill Details page. This will generate a public URL and an API key for the skill, which can be used to access the skill from any external system or application12.

In UiPath AI Center, the platform supports several types of machine learning (ML) models, including:

Out-of-the-box models from UiPath: Pre-built models designed for common automation tasks.

Models from UiPath technology partners: External models developed by UiPath’s partners.

Open-source models: Community-contributed models that can be used and adapted for various use cases.

Custom models: Models that users build and train specifically for their projects using their datasets.

This flexibility in model support ensures that organizations can leverage a wide range of machine learning capabilities to suit different automation needs.

For more details, refer to:

UiPath AI Center Documentation: AI Center Models

Machine Learning Model Types: Types of Models in UiPath AI Center

The Document Understanding Process template 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 template has an architecture decoupled from other connected automations and supports both attended and unattended processes with human-in-the-loop validation via Action Center. The template consists of the following components1:

Load Taxonomy: This component loads the taxonomy file that defines the document types and fields to be extracted. The taxonomy file can be created using the Taxonomy Manager in Studio or the Data Manager web application.

Digitization: This component converts the input document into a digital format that can be processed by the subsequent components. It uses the Digitize Document activity to perform OCR (optical character recognition) on the document and obtain a Document Object Model (DOM).

Classification: This component determines the document type of the input document using theClassify Document Scope activity. It can use either a Keyword Based Classifier or a Machine Learning Classifier, depending on the configuration. The classification result is stored in a ClassificationResult variable.

Data Extraction: This component extracts the relevant data from the input document using the Data Extraction Scope activity. It can use different extractors for different document types, such as the Form Extractor, the Machine Learning Extractor, the Regex Based Extractor, or the Intelligent Form Extractor. The extraction result is stored in an ExtractionResult variable.

Data Validation: This component allows human validation and correction of the extracted data using the Present Validation Station activity. It opens the Validation Station window where the user can review and edit the extracted data, as well as provide feedback for retraining the classifiers and extractors. The validated data is stored in a DocumentValidationResult variable.

Export: This component exports the validated data to a desired output, such as an Excel file, a database, or a downstream process. It uses the Export Extraction Results activity to convert the DocumentValidationResult variable into a DataTable variable, which can then be manipulated or written using other activities.

The Document Object Model (DOM) is a data representation of the objects that comprise the structure and content of a document on the web1. In the context of Document Understanding, the DOM is a JSON object that is generated by the Digitize Document activity, which uses the UiPath Document OCR engine to extract the text and layout information from the input document2. The DOM contains the following properties for each document3:

name: The name of the document file.

contentType: The MIME type of the document file, such as application/pdf or image/jpeg.

textLength: The number of characters in the document text.

pages: An array of objects, each representing a page in the document. Each page object has the following properties:

pageNumber: The number of the page, starting from 1.

rotation: The angle of rotation of the page, in degrees. A positive value indicates clockwise rotation, and a negative value indicates counterclockwise rotation.

language: The language code of the page, such as en or fr.

content: An array of objects, each representing a word or a line in the page. Each content object has the following properties:

type: The type of the content, either word or line.

text: The text of the content.

boundingBox: An array of four numbers, representing the coordinates of the top-left and bottom-right corners of the content, in the format [x1, y1, x2, y2]. The coordinates are relative to the page, with the origin at the top-left corner, and the unit is pixel.

confidence: A number between 0 and 1, indicating the confidence level of the OCR engine in recognizing the content.

The DOM can be used as an input for other activities in the Document Understanding framework, such as Classify Document Scope, Data Extraction Scope, or Export Extraction Results. The DOM can also be manipulated using programming code, such as JavaScript or Python, to perform custom operations on the document data.