The Blue Prism Accredited Developer Exam (AD01)

When encountering an error due to multiple similar elements on a web page with the same name, it ' s crucial to use an attribute that ensures a unique match.

Match Index (Option D) : This attribute is specifically designed to handle situations where multiple elements have similar properties. By setting the Match Index, you can specify which instance of the element should be used, ensuring a unique match.

The other options are less effective in this scenario:

Web Text (Option A) : This may not be unique if multiple elements have the same text.

Ordinal (Option B) : While it indicates the order, it’s less precise compared to Match Index.

Web Element Type (Option C) : This doesn ' t help in distinguishing between multiple similar elements.

References Consult Blue Prism ' s best practices for dealing with web automation and handling multiple similar elements on a page. The Match Index attribute is commonly recommended for these cases.

When setting the Window Text attribute for an application in Blue Prism, it ' s often helpful to use wildcards to ensure the element is consistently matched, even if the window title varies slightly. In this case, using a * at the beginning and end of the value will match any window title that contains the text " Centrix Data Solutions - Please Log In " .

Use a * at the beginning and end of the Value (Option B) : This will ensure that any leading or trailing characters in the window title will not prevent a match. For example, *Centrix Data Solutions - Please Log In* .

Other options might not be as effective:

Change the Match Type to Dynamic (Option A) : This is unnecessary if the wildcard approach works.

Position the ' ' after Solutions ' (Option C) : This does not make sense in the context provided.

Change the Match Type to Wildcard (Option D) : This would require more specific adjustments to the value itself.

References Refer to Blue Prism ' s documentation on attribute matching and the use of wildcards for ensuring reliable element identification.

In Blue Prism, Environment Locks are used to prevent concurrent access to resources. When an exception occurs, it is crucial to ensure that the lock is released to avoid deadlocks and ensure other processes can acquire the lock.

A Release Lock action should be added to the recovery logic to unlock the resource in case of an exception (Option A) : This ensures that even if an exception occurs, the lock is released, preventing any potential deadlocks and allowing other processes to acquire the lock.

Other options are not directly addressing the core issue:

Query Lock action (Option B) : This checks the lock status but does not help in releasing the lock during an exception.

Unique Lock Token (Option C) : While important for acquiring the lock initially, it does not address the release of the lock during exceptions.

Sleep action after Acquire Lock (Option D) : This helps in timing but does not handle lock release in case of an exception.

References Refer to Blue Prism ' s best practices on using Environment Locks and handling exceptions to ensure that resources are properly managed and locks are released appropriately.

Stage Logging in Production :

Logging is essential in a production environment to monitor the process execution and troubleshoot issues.

Decision Stage :

Decision stages typically evaluate conditions and direct the flow based on the evaluation.

Extensive logging for every decision can generate large log files, making it harder to find relevant information.

Best Practice :

Setting the logging to " Errors Only " ensures that only significant issues are logged, reducing log size and focusing on critical problems.

This is especially useful in a production environment where performance and log manageability are key.

References :

Blue Prism best practices for logging and monitoring in production environments.

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.

References :

Blue Prism documentation on exception handling, tagging, and logging.

In Blue Prism, wait stages are crucial to ensure that the application is in the correct state before proceeding with further actions. In this scenario:

Conditional Wait stage after the Attach page : This ensures that after attaching to the application, the process waits until the necessary elements are present before continuing. This is important because the application may take some time to load or change states.

Conditional Wait stage after the Navigate stage : This ensures that after navigating, the process waits until the target elements are available. This helps to handle any delays in the application response or page loading times.

By configuring wait stages in this manner, you ensure that the process only proceeds when the application is ready, thereby minimizing the risk of errors due to timing issues.

Other options are less optimal:

Unconditional Wait stage (Options C and D) : These do not provide the necessary checks to confirm the application ' s state and can lead to unreliable automation.

Wait stage after the Write stage (Option A) : This is less relevant if the critical steps are attaching and navigating, which are the primary steps where timing issues are likely to occur.

References Refer to Blue Prism ' s best practices on using wait stages to synchronize process execution with the application state.

Understanding the Calculation Stage:

The calculation stage in Blue Prism is used to perform calculations and store the result in a specified data item.

The expression used in the calculation stage is DateAdd(0, 1, Today()) .

Analyzing the DateAdd Function:

DateAdd(interval, number, date) is a function that adds a specified number of intervals to a given date.

The first parameter ( interval ) specifies the type of interval to add. In this case, it is 0 .

The second parameter ( number ) specifies the number of intervals to add. In this case, it is 1 .

The third parameter ( date ) specifies the starting date. In this case, it is Today() .

Interval Values in DateAdd Function:

In Blue Prism, the DateAdd function uses specific interval values:

0 for years

1 for months

2 for days

3 for hours

4 for minutes

5 for seconds

Given that the interval parameter is 0 , it means that the function will add years.

Conclusion:

The DateAdd(0, 1, Today()) expression will add 1 year to today ' s date.

Therefore, the result will be stored in the ' New Date ' data item, and the correct answer is:

A. 1 year will be added to today ' s date and the result stored in the ' New Date ' data item.

References:

Blue Prism Developer Documentation: Date Functions

Blue Prism Training Material on Calculation Stages and Date Manipulation

A sub-page in a process can have only one start stage, which is where the execution begins when the sub-page is called from another page. A sub-page cannot have zero or more than one start stages, as that would cause ambiguity or confusion in the execution flow. References: https://portal.blueprism.com/sites/default/files/2020-06/Blue%20Prism%20Certification%20-%20Developer.pdf (page 2)