UiPath-ADPv1 REFramework — 10 Questions

Question 1

Refer to the exhibit. A transaction fails due to an application exception. How many times will the REFramework retry this specific transaction?

Accepted Answer

3. When using Orchestrator queues, the REFramework's local retry mechanism (MaxRetryNumber in Config.xlsx) is typically set to 0 because Orchestrator handles retries natively. If MaxRetryNumber is set to a value greater than 0 while using Orchestrator queues, it can lead to duplicate processing. The framework logic only uses the local retry counter if the queue is not being used or if the developer has specifically configured it to do so, which is not the default behavior.

Answer

0

Answer

1

Answer

4

Question 2

Which TWO of the following are valid ways to handle a Business Rule Exception in the REFramework?

Accepted Answer

Throw a BusinessRuleException in the Process workflow.. Business Rule Exceptions (BRE) indicate data-level issues that will never succeed upon retry. Handling them requires updating the transaction status to 'Failed' in Orchestrator and logging the specific reason. This stops the retry mechanism for that item, allowing the bot to proceed immediately to the next transaction, which is essential for maintaining throughput while ensuring data integrity and accurate reporting of invalid input.

Answer

Call the 'Close All Applications' sequence immediately.

Answer

Retry the transaction immediately within a loop.

Answer

Restart the entire robot process.

Question 3

If an application exception occurs during the 'Process Transaction' state, what is the default behavior of the REFramework regarding the 'TransactionItem'?

Accepted Answer

The transaction is automatically deleted from the queue.. When an application exception occurs during the 'Process Transaction' state in the default REFramework, the Set Transaction Status activity is used to update the status of the TransactionItem in Orchestrator to 'Failed' (with the application exception details). If the item is configured for retries and the max retry number has not been reached, Orchestrator itself manages the retry, but the status set by the framework workflow is 'Failed'. However, if looking strictly at how the framework handles the item, it loops back to 'Get Transaction Data' where the retry mechanism kicks in.

Answer

The transaction is marked as 'Successful' in Orchestrator.

Answer

The transaction is abandoned, and the robot stops.

Answer

The transaction is marked as 'Retried' and the process loops back to 'Get Transaction Data'.

Question 4

Which state in the REFramework acts as the central entry point for the continuous processing loop?

Accepted Answer

Get Transaction Data. In the UiPath REFramework, the 'Get Transaction Data' state is indeed the state that determines whether the loop continues or terminates. However, the 'Process Transaction' state is also part of the loop. The 'Get Transaction Data' state is the entry point for the *transactional* loop, but the state machine transitions back to it from 'Process Transaction'. The explanation is acceptable, but the trap note should clarify that Initialization is a one-time setup state.

Answer

Initialization

Answer

Process Transaction

Answer

End Process

Question 5

A developer configures the Robotic Enterprise (RE) Framework with Get Transaction Data invoking a custom workflow that reads items from an Orchestrator queue using Get Queue Items with the Reference filter. During execution, the process repeatedly processes the same queue item after a transient application error causes a retry. Which configuration in the RE Framework is responsible for ensuring that the retried item is not treated as a new transaction?

Accepted Answer

The queue's Unique Reference setting combined with the item's Reference value, so Get Transaction Data will not return an already-processed item as a fresh transaction.. Queue-level identity is what distinguishes a retry from a new transaction. Enabling Unique Reference on the queue and populating the item's Reference with a stable business key means Orchestrator will not accept a duplicate, and Get Transaction Data will only return items still in New status. Retries then reuse the existing item rather than creating a fresh one, which is why the queue's unique reference configuration is the controlling factor.

Answer

The MaxRetryNumber asset, which limits how many times the framework will attempt to process a single transaction before marking it as failed.

Answer

The TransactionNumber variable, which is incremented in the Get Transaction Data state before each retrieval attempt.

Answer

The ShouldMarkJobAsFailed property in the SetTransactionStatus workflow, which flags the job as failed and forces Get Transaction Data to advance to the next item.

Question 6

A developer must build a UiPath automation whose main workflow follows the Robotic Enterprise Framework structure. The developer opens UiPath Studio and selects the 'Robotic Enterprise Framework' template from the New Project dialog. Which set of files does this template create to form the framework's core skeleton?

Accepted Answer

Main.xaml, Framework/InitAllSettings.xaml, Framework/InitAllApplications.xaml, Framework/GetTransactionData.xaml, Framework/Process.xaml, Framework/SetTransactionStatus.xaml, Framework/RetryCurrentTransaction.xaml, Framework/KillAllProcesses.xaml, Framework/TakeScreenshot.xaml, and Framework/CloseAllApplications.xaml. Choosing the Robotic Enterprise Framework template in Studio scaffolds a state machine in Main.xaml and a Framework folder with helper workflows for settings, applications, transaction retrieval, processing, status updates, retries, cleanup, screenshots, and application closing. This structure cleanly separates initialization, the processing loop, and teardown, letting developers focus on business logic inside Process.xaml and GetTransactionData.xaml.

Answer

Main.xaml and a set of Orchestrator assets, queues, and triggers that are automatically provisioned in the connected tenant when the template is instantiated

Answer

An empty sequence called Main.xaml plus a REFramework NuGet package reference that must be downloaded from the UiPath Marketplace before any state can run

Answer

Main.xaml, a Config.xlsx file, a project.json manifest, and a single Process.xaml that contains all states of the state machine

Question 7

A developer is creating a UiPath automation using the Robotic Enterprise Framework. The automation must process invoices from a queue in Orchestrator. During testing, the developer notices that after processing the first transaction successfully, the automation does not move to the next transaction but instead exits the loop and goes to the End Process state. What is the most likely cause of this behavior?

Accepted Answer

The TransactionItem variable is not being updated with the next queue item in the Get Transaction Data state.. The REFramework uses the TransactionItem variable to represent the current transaction. In the Get Transaction Data state, the framework retrieves the next item and assigns it to TransactionItem. If no item is assigned, the loop ends. Therefore, the failure to update TransactionItem with the next queue item is the root cause of the automation exiting prematurely.

Answer

The process is using a Business Rule Exception instead of a System Exception, causing the framework to stop.

Answer

The TransactionNumber variable is not being incremented in the Process state.

Answer

The queue in Orchestrator has not been configured with a unique reference for each transaction item.

Question 8

You are configuring a REFramework-based automation. The Get Transaction Data state calls a workflow that retrieves the next queue item. During testing, you notice that when the queue is empty, the process throws an exception instead of ending gracefully. Which property of the Get Transaction Data state's transition condition must be configured to prevent this?

Accepted Answer

The transition from Get Transaction Data to Process Transaction should be triggered when TransactionItem is not Nothing.. The Get Transaction Data state must transition to Process Transaction only when a valid transaction item has been retrieved. By checking that TransactionItem is not Nothing, the framework avoids attempting to process a non-existent item when the queue is empty. This condition ensures the process exits gracefully via End Process when no more items are available, which is the intended behavior for queue-based automations.

Answer

The transition from Get Transaction Data to Process Transaction should be triggered when TransactionNumber > 0.

Answer

The transition from Get Transaction Data to Process Transaction should be triggered when the queue has at least one item.

Answer

The transition from Get Transaction Data to End Process should be triggered when TransactionItem is Nothing.

Question 9

You are customizing the REFramework to handle a scenario where a business rule exception occurs during the Process Transaction state. You want to ensure that the transaction is marked as failed with a specific reason and that the process continues with the next transaction. Which two actions should you perform? (Choose two.)

Accepted Answer

In the Catch block for BusinessRuleException, invoke the SetTransactionStatus workflow with the status set to Failed and pass the exception message as the reason.. When a business rule exception occurs, the transaction must be marked as Failed with the exception message as the failure reason, and the SetTransactionStatus workflow should be invoked to update Orchestrator and handle logging. Marking it as Retried or Successful would be incorrect, and rethrowing would cause it to be treated as a system exception. The two correct actions ensure the transaction is properly recorded and the process continues with the next item.

Answer

In the Catch block for BusinessRuleException, set the TransactionStatus to Retried and increment the retry count.

Answer

In the Catch block for BusinessRuleException, log the exception and then rethrow it to trigger the framework's default handling.

Answer

In the Catch block for BusinessRuleException, set the TransactionStatus to Successful and continue to the next transaction.

Question 10

A developer is implementing a REFramework automation that processes expense reports. The automation must handle application exceptions that occur due to transient network issues. The developer wants to ensure that when such an exception occurs, the transaction is retried up to three times before being marked as failed. Which configuration in the REFramework should the developer modify to achieve this?

Accepted Answer

Configure the 'Max # of retries' property on the queue in Orchestrator to 3.. The REFramework leverages Orchestrator queue retry settings for per-transaction retries. When a system exception occurs, the framework calls SetTransactionStatus, which updates the queue item's status. If the queue's 'Max # of retries' is set to 3, Orchestrator will automatically retry the item up to three times. This is the standard and recommended approach for handling transient failures in REFramework.

Answer

Add a Retry Scope activity around the Process state in the Main workflow and set the number of retries to 3.

Answer

Modify the Config.xlsx file to set the 'MaxRetryNumber' setting under the 'Constants' sheet to 3.

Answer

Set the MaxRetryNumber argument in the Main workflow to 3.