Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - 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]

Look at this flow diagram from the Main Page of a process in Process Studio:

Thinking about the standard Blue Prism Process Templates, what is wrong with how this Mam Page is handling exceptions?

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:

Brittni
1 months ago
This question is like a game of 'Spot the Exception' - the more you look, the more you find! I hope the real exam isn't this much of a minefield.
upvoted 0 times
Stefany
7 days ago
B) The Exception Block in the image should be extended to cover all stages in the flow rather than just 4 sub-pages.
upvoted 0 times
...
...
Jamey
1 months ago
Between Recover and Resume, don't forget to reset the application. You don't want the next case to inherit the mess from the previous one. Maybe a trip to the 'Close Down and Start Up' pages would do the trick.
upvoted 0 times
Demetra
5 days ago
E) Between the Recover and Resume stages there should be logic to reset the application ready for the next case to be worked. For example, this could call the Close Down and Start Up pages.
upvoted 0 times
...
Raul
18 days ago
C) It would be better to remove the Exception Block and recover, resume logic, and instead handle any exceptions in the sub-pages. Flag data items could instead be passed up as output parameters from the sub-pages informing the Main Page flow if an exception has occurred.
upvoted 0 times
...
...
Mel
2 months ago
Wait, there's no concurrent exception logic? That's just asking for trouble. Every item in the Work Queue could end up with the same System Exception. Yikes!
upvoted 0 times
Lai
24 days ago
D) The exception handling in the image does not contain any concurrent exception logic. This means there is nothing stopping every item in the Work Queue being marked with the exact same System Exception.
upvoted 0 times
...
Frank
1 months ago
C) It would be better to remove the Exception Block and recover, resume logic, and instead handle any exceptions in the sub-pages. Flag data items could instead be passed up as output parameters from the sub-pages informing the Main Page flow if an exception has occurred.
upvoted 0 times
...
Arlie
1 months ago
B) The Exception Block in the image should be extended to cover all stages in the flow rather than just 4 sub-pages.
upvoted 0 times
...
...
Michael
2 months ago
I think option C is the way to go. Handling exceptions in the sub-pages and passing up relevant data items is a better approach than the centralized Exception Block.
upvoted 0 times
Aja
1 months ago
Yes, that could provide a more robust exception handling process.
upvoted 0 times
...
Novella
1 months ago
That's a good point. Maybe a combination of handling exceptions in sub-pages and adding concurrent exception logic would be the best approach.
upvoted 0 times
...
Laquanda
1 months ago
But what about the concurrent exception logic mentioned in option D?
upvoted 0 times
...
Lynelle
2 months ago
I agree, handling exceptions in the sub-pages seems more efficient.
upvoted 0 times
...
...
Dana
2 months ago
The main issue here seems to be the limited scope of the Exception Block. Covering just 4 sub-pages is not enough, it should be extended to handle exceptions across the entire process flow.
upvoted 0 times
Garry
1 months ago
C) It would be better to remove the Exception Block and recover, resume logic, and instead handle any exceptions in the sub-pages. Flag data items could instead be passed up as output parameters from the sub-pages informing the Main Page flow if an exception has occurred.
upvoted 0 times
...
King
2 months ago
B) The Exception Block in the image should be extended to cover all stages in the flow rather than just 4 sub-pages.
upvoted 0 times
...
...
Izetta
2 months ago
I believe the Main Page flow should include concurrent exception logic.
upvoted 0 times
...
Lindsay
2 months ago
I agree with Pauline, it would be better to handle exceptions in the sub-pages.
upvoted 0 times
...
Pauline
2 months ago
I think the Exception Block should cover all stages in the flow.
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