AD01 Exam Dumps : Blue Prism Accredited Developer Exam

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.

ReferencesConsult 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.

• Stage Logging in Production:
• Decision Stage:
• Best Practice:

References:

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

The provided diagram represents an Action page in a Business Object that is used to place orders. According to best practices for Object Design in Blue Prism, actions should primarily focus on interacting with the application rather than containing business rules or decision-making logic. The following points explain why Option D is the correct answer:

• Avoid applying business rules and decision-making logic in an Action (Option D): Business rules and decision-making should be handled in Process Studio, not in Object Studio. The decision regarding "Quantity Under Limit?" in the diagram is a business rule and should be part of the process logic, not the object logic.

Other options are essential best practices but are not violated here:

• Use a conditional Wait stage to confirm the screen change (Option A): This is followed as the diagram shows a Wait stage confirming the screen change.
• The timeout of the Wait stage should lead to a System Exception (Option B): This is followed as the diagram shows a system exception being thrown upon a timeout.
• An action page should first confirm if the application is connected (Option C): This is followed as the action begins by checking the connection to the "New Order Window."

ReferencesRefer to Blue Prism's best practices for Object Design, which emphasize separating process logic and object interaction logic.