Deal of The Day! 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:

Flo
23 days ago
Hmm, I'm leaning towards A) and E) - the column filters and stage logging seem like the most reliable way to cover all our bases. Though I have to admit, the 'Scan Processes' feature sounds like something straight out of Ghostbusters!
upvoted 0 times
Avery
7 days ago
A) Use the column filters available within Blue Prism Settings > Audit > Process Log settings
upvoted 0 times
...
...
Cherelle
28 days ago
I believe option B and D could also be useful in tagging and identifying Exception items.
upvoted 0 times
...
Valentine
29 days ago
Wow, this question is really testing our Blue Prism knowledge! I think E) is a must, and then maybe C) to make sure we're not missing any exceptions. Gotta catch 'em all, ya know?
upvoted 0 times
...
Kandis
1 months ago
I agree with Chantell, having stage logging enabled and using column filters would be helpful.
upvoted 0 times
...
Olive
1 months ago
I'm not sure about B), tagging the exception details prior to marking an item as an exception feels a bit convoluted. I'd go with A) and D) - using the column filters and the scan processes feature seems more straightforward.
upvoted 0 times
Pura
13 days ago
Yeah, tagging the exception details before marking an item as an exception does seem a bit complicated.
upvoted 0 times
...
Emilio
18 days ago
I agree, using the column filters and scan processes feature does seem more straightforward.
upvoted 0 times
...
...
Chantell
1 months ago
I think option A and E are the best recommendations.
upvoted 0 times
...
Mari
1 months 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
Felicitas
11 days ago
B) Call the Exception Stage details and tag them to the Item prior to Mark Item as Exception
upvoted 0 times
...
Yvette
20 days ago
A) Use the column filters available within Blue Prism Settings > Audit > Process Log settings
upvoted 0 times
...
Aracelis
24 days ago
E) Ensure that the Stage logging is enabled within each Exception Properties
upvoted 0 times
...
Jimmie
1 months ago
C) Loop through the Work Queue items in Exception and tag with the Exception Details
upvoted 0 times
...
...

Save Cancel