Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Blue Prism Exam AD01 Topic 1 Question 85 Discussion

Actual exam question for Blue Prism's AD01 exam
Question #: 85
Topic #: 1
[All AD01 Questions]

The Process Controller needs to be able to view Exception items from both the Work Queue screen within the Control room, and from the Session Logs According to best practice, which TWO options would the Developer recommend?

Show Suggested Answer Hide Answer
Suggested Answer: B, E

Tagging Exception Items:

By calling the Exception Stage details and tagging them to the item before marking it as an exception, it ensures that detailed information about the exception is captured and can be viewed later. This helps in identifying the cause of the exception and provides valuable context.

Stage Logging:

Enabling stage logging within each exception properties ensures that all exception details are logged. This allows the Process Controller to view detailed exception information from the session logs, providing a comprehensive view of what went wrong.

Benefits:

These two approaches ensure that exception details are both tagged to the work queue items and logged in the session logs, making it easier for the Process Controller to review and analyze exceptions from different interfaces within Blue Prism.


Blue Prism documentation on exception handling, tagging, and logging.

Contribute your Thoughts:

Chantell
3 days ago
I think option A and E are the best recommendations.
upvoted 0 times
...
Mari
4 days ago
C) and E) seem like the best options to me. Looping through the work queue and enabling stage logging would cover the requirement to view exceptions from both the work queue and session logs.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77