Blue Prism Updated AD01 Exam Questions and Answers by usman

When working with the Blue Prism Application Modeller, the visibility of an element is critical for ensuring that it can be consistently interacted with by Blue Prism. The "Screen Visible" attribute determines whether the element is currently visible on the screen. However, this attribute can sometimes cause issues if the element is off-screen or hidden but still needs to be interacted with by Blue Prism.

• Screen Visible (Option B): Unticking this attribute ensures that Blue Prism can interact with the element even when it is not visible on the screen. This helps in maintaining consistent visibility and interaction with the element regardless of its on-screen status.

The other attributes are important for identifying and interacting with the element:

• Window Text (Option A): This attribute is necessary to identify the text within the window.
• Visible (Option C): This indicates whether the element is visible; unticking this might cause inconsistency.
• Class Name (Option D): This attribute helps identify the type of UI element, crucial for correct interaction.

ReferencesBlue Prism's best practices for application modelling and attribute selection emphasize maintaining consistency and reliability in element interaction by carefully managing visibility attributes.

Reason: This is because when we are running the process in testing and development phase at time the speed of running the process is slow, that’s why it ran properly and when we haven’t give the proper wait stage and when the process ran in control room the exception occurs as the process ran in full speed so the process is not having the time to wait.

This is mentioned in the Process creation exercise or Lifecycle exercise.

• Credential Retrieval:
• Cause of Exception:
• Steps to Fix:

References:

• Blue Prism documentation on using the Credential Manager and best practices for secure credential handling.