A developer automated a process with the following logic: each queue item contains a filepath to an Excel file. If the required file exists, robot needs to upload it on Sharepoint. Otherwise, the transaction cannot be considered a success.
What is the best approach if the required file does not exist?
A . Set status of the transaction to Business Rule Exception. Wrap Path Exists activity in Try Catch.
B. Set status of the transaction to Business Rule Exception. Configure queue to retry Business Rule Exception transactions 3 times.
C. Set status of the transaction to Business Rule Exception. Configure robot to notify the responsible person that the required file is missing.
D. Set status of the transaction to System Exception. Configure queue to retry System Exception transactions 3 times.
Answer: C
Explanation:
A Business Exception describes an error rooted in the fact that certain data which the automation project depends on is incomplete or missing.
Retrying the transaction does not yield any chance of solving the issue, and there are other better courses of action, such as notifying the human user of this error.
By default, Orchestrator does not retry transactions which are failed due to Business Exceptions. This happens because an inconsistency between the transaction value and the business requirement means that there might be errors in the initial data which the queue items were created from. Additional actions by human users might be required to fix this type of issue, and logging this type of exception and notifying the responsible person can be useful.
UiPath Documentation
Exam Topic: Describe the differences between Dispatcher and Performer, how the Dispatcher is used to upload transaction items, and how the Performer is used to consume the queues and process the transactions. Differentiate between using Application Exceptions and Business Rule Exceptions.
Latest UIPATH-ARDV1 Dumps Valid Version with 207 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund