Pass the Blue Prism Developer AD01 Questions and answers with ExamsMirror

Analysis of the Launch Action:

The action involves launching an order processing application, which brings up a login screen requesting the user's login details.

The flow in the question shows a 'Launch' stage and an 'End' stage with no intermediate stages.

Blue Prism Best Practices:

According to Blue Prism best practices, after launching an application, it is essential to verify that the application has loaded successfully and is ready for further interaction.

This verification is typically done using a wait stage to check for the presence of specific elements that confirm the application is ready, in this case, elements on the login screen.

Reasoning for the Wait Stage:

The Wait stage ensures that the login screen has fully loaded and the elements are available for interaction.

This prevents the automation process from proceeding to the next steps too quickly, which could lead to errors if the elements are not yet ready.

Implementation:

Insert a Wait stage immediately after the Launch stage.

Configure the Wait stage to check for a specific element on the login screen, such as the 'Staff Number' field or the 'Sign In' button.

Only proceed to the next stages (entering login details, etc.) once the Wait stage confirms the presence of the required elements.

References:

Blue Prism Developer Documentation: Best Practices for Wait Stages

Blue Prism Training Material on Login Automation Procedures

Understanding Blue Prism Stages:

Blue Prism automation involves various stages that represent different actions and decisions in a process or object. These stages are used to build process flows in both Process Studio and Object Studio.

Certain stages are common to both studios, while some are specific to one.

Identification of Stages in the Image:

Option A: Decision Stage

Option B: Calculation Stage

Option C: Multi-Calculation Stage (a combination of calculations)

Option D: Data Item

Option E: Process Stage

Option F: Navigate Stage (specific to Object Studio)

Stages Common to Both Process Studio and Object Studio:

Decision Stage (Option A): Used to make decisions based on conditions.

Calculation Stage (Option B): Used to perform calculations.

Multi-Calculation Stage (Option C): Represents multiple calculations grouped together.

Data Item (Option D): Represents variables or data items used in the process.

Process Stage (Option E): Used to invoke sub-processes or other processes within a main process.

Stage Specific to Object Studio:

Navigate Stage (Option F): Used to interact with applications, specific to Object Studio.

References:

Blue Prism Developer Documentation: Process and Object Studio Stages

Blue Prism Training Material on Building Processes and Objects

Understanding Priorities:

In Blue Prism, work queue items with a lower priority value are processed before those with a higher priority value.

Setting Priorities:

To ensure that Business Customer cases are worked first, the priority for these cases should be set to the lowest value.

For Business cases, set the priority to "0".

For all other cases (Personal and Joint), set the priority to "1".

Implementation:

While adding items to the work queue, use the Add to Queue action to set the priority.

Ensure Business cases have priority "0" and others have priority "1".

References:

Blue Prism documentation on work queue priorities.