UiPath-SAIv1 Sample Questions Answers

The Taxonomy Manager is a tool that enables you to create and edit a Taxonomy file, which is an XML file that defines the document types and fields that are relevant for your automation project1. The Taxonomy file is used by the Classify Document Scope and Data Extraction Scope activities to perform document classification and data extraction, respectively2. The Taxonomy Manager allows you to add, remove, rename, or reorder document types and fields, as well as specify the data type, format, and validation rules for each field3. The Taxonomy Manager also provides a preview of the Taxonomy file and a validation feature to check for errors or inconsistencies.

References:

1: About Taxonomy Manager 2: About Document Understanding Framework 3: Using the Taxonomy Manager : Taxonomy Manager User Interface Description

Labels in UiPath Communications Mining are user-defined categories that can be applied to communications data, such as emails, chats, and calls, to identify the topics, intents, and sentiments within them1. Labels are trained using supervised learning, which means that users need to provide examples of data that belong to each label, and the system will learn from these examples to make predictions for new data2. However, not all labels are equally easy to train, and some may require more examples than others to achieve good performance. Labels that have bias warnings are those that have relatively low average precision, not enough training examples, or were labelled in a biased manner3. Precision is a measure of how accurate the predictions are for a given label, and it is calculated as the ratio of true positives (correct predictions) to the total number of predictions made for that label. A label with 100% precision means that all the predictions made for that label are correct, but it does not necessarily mean that the label is well-trained. It could be that the label has very few predictions, or that the predictions are only made on a subset of data that is similar to the training examples. This could lead to overfitting, which means that the label is too specific to the training data and does not generalize well to new or different data. Therefore, labels with 100% precision may still have bias warnings if they lack training examples, because this indicates that the label is not representative of the underlying data distribution, and may miss important variations or nuances that could affect the predictions. To improve the performance and reduce the bias of these labels, users need to provide more and diverse examples that cover the range of possible scenarios and expressions that the label should capture.

References: 1: Communications Mining Overview 2: [Creating and Training Labels] 3: Understanding and Improving Model Performance : [Precision and Recall] : [Overfitting and Underfitting] : Fixing Labelling Bias With Communications Mining

According to the UiPath documentation portal1, the Export stage of the Document Understanding Framework is the final stage of the document processing workflow, where the extracted data is converted to a dataset or to a customized format, such as Excel, JSON, or XML. The Export stage enables you to easily export data for training ML models, using the Export files dialog box in Data Manager or Document Manager. The Export stage also allows you to export the schema of the fields and their configurations, which can be imported into a different session. The Export stage supports different export options, such as current search results, all labeled, schema, or all. The Export stage also provides validation rules, such as requiring at least 10 labeled documents or pages for each field, and at least one document for each classification option1. Therefore, option A is the correct answer, as it describes the main function and benefit of the Export stage. Option B is incorrect, as it refers to the Data Validation stage, which is the previous stage of the document processing workflow, where a human can review and correct the extracted data using the Validation Station or the Present Validation Station activities2. Option C is incorrect, as it refers to the Classification stage, which is the second stage of the document processing workflow, where the document is classified as one of the predefined document types using the Classify Document Scope activity and a classifier of choice3. Option D is incorrect, as it refers to the Digitization stage, which is the first stage of the document processing workflow, where the text is extracted out of the image document using OCR (Optical Character Recognition) using the Digitize Document activity and an OCR engine of choice.

References: 1 Document Understanding - Export Documents 2 Document Understanding - Data Validation 3 Document Understanding - Classification Document Understanding - Digitization

• Create the new label by assigning it at least once. This is the initial step to introduce a new category or classification within your data taxonomy.
• Search for instances in the reviewed data where the new label should have been assigned, and apply the label accordingly. This step is crucial for maintaining consistency across your data set.
• Use 'Missed Label' to find all additional missing examples in the reviewed data. This action helps in identifying and rectifying any instances that may have been overlooked during the initial review.
• Check validation to ensure the label is performing as expected, and follow recommended actions if further training is required. Validation is key to assess the accuracy and performance of the new label within the system.

According to the UiPath documentation1, the generic Document Understanding ML Package supports data extraction from any type of structured or semi-structured documents, building an ML model from scratch. The supported languages for this package are Latin-based languages, Cyrillic languages, Greek left-to-right, and Japanese (Preview). Additionally, the documentation23 also mentions that the package can support Chinese with the use of an OCR that supports that language. Therefore, the correct answer is D.

References: Document Understanding - Supported Languages, Document Understanding - ML Packages, Document Understanding - ML Packages.

Recall is a metric that measures the proportion of all possible true positives that the model was able to identify for a given concept1. A true positive is a case where the model correctly predicts the presence of a concept in the data. Recall is calculated as the ratio of true positives to the sum of true positives and false negatives, where a false negative is a case where the model fails to predict the presence of a concept in the data. Recall can be interpreted as the sensitivity or completeness of the model for a given concept2. For example, if there are 100 verbatims that should have been labelled as ‘Request for information’, and the model detects 80 of them, then the recall for this concept is 80% (80 / (80 + 20)). A high recall means that the model is good at finding all the relevant cases for a concept, while a low recall means that the model misses many of them.

References: 1: Recall 2: Precision and Recall

 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

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.jpg

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'.
• Using an Assign activity, assign the given non-default taxonomy text file path to the most recent variable created.
• 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'.
• 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.

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

To enable a remote knowledge worker to validate the extracted data from documents in Action Center, the automation workflow needs to include the following activities12:

• Create Document Validation Action: This activity creates an action of type Document Validation in Orchestrator Action Center, and returns an action object as output. The action object contains the information needed to resume the workflow after the human validation is completed. The input properties of this activity include the action details, such as title, priority, catalog, and folder, and the document validation data, such as the document object model, the document text, the taxonomy, and the automatic extraction results.
• Wait for Document Validation Action and Resume: This activity suspends the execution of the workflow until the human validation is done in Action Center, and then resumes it with the updated extraction results. The input property of this activity is the action object obtained from the Create Document Validation Action activity. The output property is the validated extraction results, which can be used for further processing or exporting.

References: 1: Create Document Validation Action 2: Wait for Document Validation Action and Resume

 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

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

References: 1: Machine Learning Extractor - UiPath Activities 2: Machine Learning Classifier Trainer - UiPath Document Understanding 3: Data Extraction - UiPath Document Understanding

According to the UiPath documentation, a dataset is a folder of storage containing arbitrary sub-folders and files that allows machine learning models in your project to access new data points. You can edit a dataset’s name, description, or content from the Datasets > [Dataset Name] page, by clicking Edit dataset. However, you can only edit a dataset if it is not currently being used in an active pipeline. A pipeline is a sequence of steps that defines how to train, test, and deploy a machine learning model. If a dataset is being used in an active pipeline, you will see a lock icon next to it, indicating that it cannot be edited. You can either wait for the pipeline to finish or stop it before editing the dataset.

References:

• AI Center - Managing Datasets
• AI Center - About Datasets
• AI Center - About Pipelines

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 the Classify 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.

References: Document Understanding Process: Studio Template, Document Understanding Process - New Studio Template, Document Understanding Process Template in UiPath Studio

According to the UiPath Communications Mining documentation, reviewing and applying entities is a crucial step for improving the accuracy and performance of the entity extraction models. When reviewing entities, users should check all of the predicted entities within a paragraph, as well as any missing or incorrect ones. Users can accept, reject, edit, or create entities using the platform’s interface or keyboard shortcuts. Users can also change the entity type if the value is correct but the type is wrong. Reviewing and applying entities helps the platform learn from the user feedback and refine its predictions over time. It also helps users assess the automation potential and benefit of the communications data.

References:

• Communications Mining - Reviewing and applying entities
• Communications Mining - Improving entity performance

 According to the UiPath documentation portal1, the DocumentPath property in the Classify Document Scope activity accepts the path to the document you want to validate. This field supports only strings and String variables. The supported file types for this property field are .png, .gif, .jpe, .jpg, .jpeg, .tiff, .tif, .bmp, and .pdf. Therefore, option B is the correct answer, as it contains four of the supported file types. Option A is incorrect, as .psd is not a supported file type. Option C is incorrect, as .raw is not a supported file type. Option D is incorrect, as .eps is not a supported file type.

References: 1 Activities - Classify Document Scope - UiPath Documentation Portal

Main-ActionCenter is a workflow that allows you to create and manage Document Understanding actions in Action Center, which is a web application that enables human intervention in automation processes. You can use Main-ActionCenter when you want to test your Document Understanding process locally, or when you want to implement an attended process that requires human validation or classification of documents. Main-ActionCenter is not recommended for unattended processes, as they do not involve human interaction.

References: Action Center - Document Understanding activities, Document Understanding Process 22.10 now in General Availability!, How to Start a UiPath Document Understanding Project

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

According to the UiPath documentation, the recommended number of samples for the classification fields depends on the number of document types and layouts that you want to classify. The more document types and layouts you have, the more samples you need to cover the diversity of your data. However, a general guideline is to have at least 20-50 document samples from each class, as this would provide enough data for the classifiers to learn from12. A large number of samples per layout is not mandatory, as the classifiers can generalize from other layouts as well3.

References: 1: Document Classification Training Overview 2: Document Classification Training Related Activities 3: Training High Performing Models

 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.