UiPath Updated UiPath-ADPv1 Exam Questions and Answers by roux

UiPath Integration Service is the component of the UiPath Platform that makes the automation of third-party applications much easier by standardizing authorization and authentication, helping you manage API connections and also allowing faster integration into SaaS platforms1. By using pre-built connectors, the development of automation projects in UiPath Studio is more simple and more consistent, regardless of the third-party applications you are automating1. Some of the advantages of pre-built connectors are:

• They enable automation with an out-of-the-box library of connectors for popular applications such as Salesforce, Slack, Microsoft Office 365, SAP, ServiceNow, and Google G Suite23.
• They help setting up and managing connections easily with standardized authentication methods such as OAuth 2.0, Basic, API Key, and Custom1.
• They enable kicking off automations with server-side triggers or events, such as receiving an email, creating a record, or updating a field1.
• They provide curated activities and events (with additional data filters) for ease of use in UiPath Studio1.
• They simplify automation design by providing a uniform experience across all Studio designers1.
• They integrate across all UiPath Platform product solutions, such as UiPath Orchestrator, UiPath Assistant, UiPath Action Center, and UiPath Apps3.

References:

• Introducing UiPath Integration Service | UiPath
• Integration Service - Introduction - UiPath Documentation Portal
• Integration Service - Connectors - UiPath Documentation Portal
• New UiPath Integration Service | UiPath

 UiPath handles different dependency versions for multiple running processes that run at the same time by using the concept of isolation. This means that each running process uses its own required version of the dependency, without affecting or being affected by other processes. This ensures that the processes run smoothly and consistently, regardless of the dependency versions. The isolation is achieved by using the NuGet protocol, which allows the robot to download and store the dependencies in a local cache folder. The robot then loads the dependencies from the cache folder into separate application domains for each process, creating isolated environments for each process. References: [Managing Dependencies], [About the NuGet Protocol]

The Verbose logging level includes the following information by default:

• Execution Started log entry - generated every time a process is started.
• Execution Ended log entry - generated every time a process is finalized.
• Transaction Started log entry - generated every time a transaction item is obtained by the robot from Orchestrator.
• Transaction Ended log entry - generated every time the robot sets the transaction status to either Success or Failed.
• Activity Information log entry - generated every time an activity is started, faulted or finished inside a workflow.
• Arguments and Variables Information log entry - show values of the variables and arguments that are used.

The Verbose logging level is the most detailed one and it is useful for debugging purposes, as it provides a lot of information about the execution flow and the data used by the robot. However, it also generates a lot of log entries, which can affect the performance and the storage space of the robot and Orchestrator. References: [Logging Levels]