UiPath-SAIAv1 Exam Dumps : UiPath Specialized AI Associate Exam (2023.10)

The Document Understanding Process uses two types of synchronization mechanisms to prevent multiple robots from writing in a file at the same time: file locks and queues. File locks are used to ensure that only one robot can access a file at a time, while queues are used to store the information extracted from the documents and to avoid data loss or duplication. The process uses the following activities to implement these mechanisms:

File Lock Scope: This activity creates a lock on a file or folder and executes a set of activities within it. The lock is released when the scope ends or when an exception occurs. This activity ensures that only one robot can read or write a file or folder at a time, and prevents other robots from accessing it until the lock is released.

Add Queue Item: This activity adds an item to a queue in Orchestrator, along with some relevant information, such as a reference, a priority, or a deadline. The item can be a JSON object, a string, or any serializable .NET type. This activity ensures that the information extracted from the documents is stored in a queue and can be retrieved by another robot or process later.

Get Queue Items: This activity retrieves a collection of items from a queue in Orchestrator, based on some filters, such as status, reference, or creation time. The items can be processed by the robot or passed to another activity, such as Update Queue Item or Delete Queue Item. This activity ensures that the information stored in the queue can be accessed and manipulated by the robot or process.

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.

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.