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 Main Page is handling exceptions?
A) There is nothing wrong with the Main Page flow shown in the image, it is a copy of Blue Prism's standard Process Template.
B) The Exception Block in the image should be extended to cover all stages in the flow rather than just 4 sub-pages.
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.
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.
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.

Question

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 Main Page is handling exceptions?
A) There is nothing wrong with the Main Page flow shown in the image, it is a copy of Blue Prism's standard Process Template. 
B) The Exception Block in the image should be extended to cover all stages in the flow rather than just 4 sub-pages. 
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. 
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. 
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.

Quizplus · Accepted Answer

The Answer of 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 Main Page is handling exceptions?
A) There is nothing wrong with the Main Page flow shown in the image, it is a copy of Blue Prism's standard Process Template. 
B) The Exception Block in the image should be extended to cover all stages in the flow rather than just 4 sub-pages. 
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. 
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. 
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.

Look at This Flow Diagram from the Main Page of a Process