UiPath-ADPv1 Flashcards — Free UiPath Automation Developer Professional Study Cards

Assign a shortcut key directly to the process configuration inside UiPath Assistant so the user can invoke it instantly.

Configuring a custom shortcut directly within UiPath Assistant allows users to launch attended automations instantly without navigating menus. This method ensures seamless human-in-the-loop collaboration by letting operators initiate background or foreground tasks directly from their active workspace, drastically minimizing operational friction and improving overall daily productivity across enterprise desktop environments.

The user is missing the 'Folders.View' permission.

The policy grants permission to create a job, but it lacks the necessary 'View' permission on the process itself or the folder. Orchestrator's security model requires users to have read access to the resource (process) to initiate an action against it. Without the 'Folders.View' or 'Processes.View' permissions, the Create action fails despite having explicit job creation rights defined in the policy.

TransactionNumber > TotalItems

In a state machine, conditions must be defined as boolean expressions. 'TransactionNumber > TotalItems' is the correct syntax for evaluating this comparison. This logic is foundational for managing loop-like structures in State Machines, ensuring that the process terminates gracefully once all work items have been successfully processed, which is a core requirement for the Robotic Enterprise Framework (REFramework) to function correctly in production environments.

Initialization

The Initialization state is the first phase of the REFramework workflow. It serves to load configuration parameters from the spreadsheet and establish connections to external applications. This is critical because downstream states like Get Transaction Data and Process Transaction rely on the environment being correctly configured. Failing here prevents the bot from proceeding, ensuring that errors are caught early before attempting to process business data.

Set the queue's Max Retry to 3 and use the Set Transaction Status activity with the status Failed in the catch block, allowing Orchestrator to automatically retry the transaction.

Orchestrator queues support automatic retries when a transaction is marked as Failed. The Max Retry property defines how many times a failed item will be retried. The developer must use Set Transaction Status with the Failed status in the catch block to trigger this mechanism. This ensures the item is retried up to the configured limit without creating duplicate queue items or relying on local retry logic.

Refine the prompt by explicitly describing the required argument names and data types for each activity.

Refining Autopilot outputs requires an iterative prompt engineering approach. By providing context-specific instructions, such as explicit variable names and data types, the developer guides the model toward more accurate architectural patterns. This is vital in enterprise environments where maintaining modularity and strict type safety is required to prevent runtime exceptions. Simply regenerating without context will likely yield the same structural errors, whereas prompt refinement addresses the underlying logic gaps in the model's interpretation.

Insert a Log Message activity with an informative string including the variable value.

Using the Log Message activity with a Trace level or utilizing the 'Write Line' activity combined with an output file allows you to capture runtime data values asynchronously. This is vital in production or complex environments where standard breakpoints disrupt timing-sensitive application interactions. By logging state changes to a file or Orchestrator, developers can reconstruct the execution path post-mortem without relying on active session control, ensuring minimal impact on process performance.

Configure the HTTP Request activity to stream the response directly into a JsonTextReader instance for token-based processing.

Deserializing large JSON payloads entirely into memory is a primary cause of resource exhaustion in automation workflows. By utilizing Newtonsoft.Json with JsonTextReader, developers can stream the JSON data token by token instead of loading the complete document structure into memory simultaneously. This memory-efficient architecture ensures long-running unattended processes remain stable and scale effectively when consuming massive external payloads from enterprise REST endpoints.

Use the Image automation activity with a stable anchor for the target.

Image-based automation is the standard fallback for legacy applications lacking accessibility frameworks. By combining Image anchors with relative positioning, you ensure the robot can locate target elements even if the window layout shifts slightly. This approach is critical for legacy systems where traditional selectors are unavailable, as it relies on visual patterns rather than underlying DOM structure, ensuring stability in non-standard UI environments.

Apply the .AsEnumerable().Where(Function(r) r("Status").ToString = "Active" AndAlso CInt(r("Stock")) > 50).CopyToDataTable() method.

Using LINQ with the .Where() method is the standard for high-performance filtering in UiPath. It executes in memory, avoiding the overhead of iterating through rows using a For Each loop. This approach is critical when dealing with datasets containing thousands of records, as it reduces automation execution time and memory consumption significantly, ensuring the process remains responsive under load.