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.
So there is a mistake, since correct answer is D. Presented template is shown in materials from BP training, but it's not the final version - some improvemts can be done, like in answer D
I vote for A. Because this flow can be found in Best Practices document on page 17 and 18,
D is also seemed correct but this flow can be stopped manually by "Stop ?" decision stage if concurrent exception occurred. And E is also seemed correct but in Best Practices document resetting application logic is added on subpages. (page 19)
Answer should be D and E
D Because - In the diagram the action is used to mark the item as exception where as the standard template has a page called which has concurrent exception handling and mark exception logic inside
D Because - after the recover stage there should be a calculation variable to capture the type and details of the exceptions so that we can mark the item as exception accordingly.
E is not correct, since such logic (for resetting applications) should included after 'Mark item as exception' - otherwise, there is a chance to not execute 'Mark item as exceptio' if resetting aplication fails
E is not correct, since such logic (for resetting applications) should included after 'Mark item as exception' - otherwise, there is a chance to not execute 'Mark item as exceptio' if resetting aplication fail
I think it's D. In my opinion Option A is not true because the 'Mark Item as Exception' is a stage and not the page like shown in this image. The BP Process Template calls 'Mark Item as Exception'' page where it does categorize the errors.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
naive91
Highly Voted 2 years, 3 months agoAscar
1 year, 11 months agoLH1213
Most Recent 1 month agoRadekRPA
3 months, 2 weeks agorpa2
3 months, 2 weeks agoIngvarn
5 months, 2 weeks agotdesbarres
1 year agobrocol
1 year, 3 months agoMasaoF
1 year, 4 months agopwrcert
1 year, 11 months agoAscar
1 year, 11 months agosogoku_ichi_2907
2 years agosogoku_ichi_2907
2 years agoAscar
1 year, 11 months agokrrish0
2 years, 1 month agoAscar
1 year, 11 months agoZerohash
2 years, 2 months agoPM__
2 years, 3 months agocoolala
2 years, 5 months agocoolala
2 years, 5 months agoabain89
2 years, 10 months ago