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?

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

Comment: *

Name: *

Email: *

Verification: *

Consider the following process flow from a sub-page of a process:

What is the problem with this sub-page flow?

• A.For better visibility of the process logic the flow steps shown in the image should be on the main page rather than in a sub-page of the process.
• B.The exception stage within the flow should be removed and replaced with an End stage that returns the found data item as an output parameter.
• C.There is nothing wrong with the sub-page flow shown in this image.
• D.The sub-page process flow is missing any retry exception handling that should exist where a process calls object actions that interface with an application.

Comment: *

Name: *

Email: *

Verification: *

Consider the following diagram from an object studio action:

What is the problem with this flow?

• A.There is nothing wrong with the object flow shown in this image.
• B.There is a risk of the flow causing an infinite loop
• C.There should be a wait stage at the end of the flow, before the end stage to ensure the flow logic has worked correctly
• D.The Exception Block should be removed from the page so that all exceptions on that page can be recovered.

Comment: *

Name: *

Email: *

Verification: *

Study the following image showing part of the flow within a process:

What problems do you see with the process flow? (Choose two.)

• A.There is a missing Recover stage on one of the routes through the flow.
• B.There is a missing Resume stage on one of the routes through the flow.
• C.The Retry Count is not being incremented for each retry.
• D.If an exception is thrown in the Cancel Reservation page and is allowed to bubble up to be caught by the Recover stage, the Create Reservation action won’t be retried.

Comment: *

Name: *

Email: *

Verification: *

Study the following diagram which is an extract from a process being tested in Process Studio:

There are no breakpoints in the "Access Customer Account" subpage however there is an error.
What will happen if you choose to step over (F10) when debugging the process?

• A.The process will work all stages in the "Access Customer Account" page until the error is thrown and then focus will move to the "Recover1" stage.
• B.The process will work all stages in the "Access Customer Account" page until the error is thrown and then focus would move to the appropriate recover stage on the "Access Customer Account" page.
• C.The process will work all stages in the "Access Customer Account" page until the error is thrown and then focus will move to the "Get Customer Detail" stage.
• D.The process will work all stages in the "Access Customer Account" page until the error is thrown and then focus will move to the stage containing the error on the "Access Customer Account" page.

Comment: *

Name: *

Email: *

Verification: *