Blue Prism AD01 - Blue Prism Accredited Developer Exam

In Blue Prism, collection columns are referenced in expressions using dot notation. This allows for dynamic and precise access to specific data within a collection.

Expressions (Option B): When you need to reference a specific column in a collection within an expression, you use dot notation. For example, if you have a collection named EmployeeData with a column named FirstName, you would reference it as EmployeeData.FirstName in an expression.

The other options are not correct in this context:

Loop Properties (Option A): While loops interact with collections, they do not use dot notation to reference columns.

Work Queue (Option C): Work queues handle items as a whole and do not use dot notation for columns within collections.

Business Object (Option D): While Business Objects can manipulate collections, the specific reference to collection columns using dot notation is primarily used in expressions.

ReferencesConsult Blue Prism's documentation on expressions and how to work with collections within them for precise data referencing using dot notation.

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.

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

Active Directory Integration:

With Active Directory Integration, user authentication can be managed through the organization's Active Directory, enabling better user management and security.

Encrypt and Decrypt Work Queue Item Data:

With the Credentials Manager functionality deployed, it is possible to encrypt and decrypt sensitive data within work queue items, enhancing data security.

Functionality Added:

These functionalities enhance security and streamline user management in future automations.

References:

Blue Prism documentation on Credentials Manager and its integration with Active Directory and work queue item encryption.

Revisiting the Issue:

Similar to Question No: 130, the developer is unable to pass collection data as an input parameter because the collection is not visible under the available data items.

Analyzing the Possible Reasons:

Option A: As previously explained, collections need to be set to global to be visible and usable as input parameters.

Option B: A block surrounding the collection does not impact its visibility.

Option C: The number of fields in a collection does not affect its visibility as an input parameter.

Option D: Undefined fields in a collection cause functional issues but not visibility issues.

Conclusion:

The reason the collection is not visible as an input parameter is because A. The referenced Collection is not set to global.

References:

Blue Prism Developer Documentation: Collections and Global Data Items

Blue Prism Training Material on Data Item Scope and Visibility

Session Variables:

Session Variables are data items whose values can be changed while a process is running.

Updating Session Variables:

Variable Repository in System Manager (Option A & B): This refers to managing variables at the system level, which is not used for updating running process variables directly.

Calculation Stage (Option C): This can be used within the process to update the value of a session variable during runtime.

Control Room (Option D): Allows operators to update session variable values for running processes via menu options.

Conclusion:

The correct methods to update the value of a data item exposed as a 'Session Variable' while the process is running are:

C. Through a Calculation stage in the same process.

D. Selecting the running Process in Control Room and then using the menu options to push a new value to the data item.

References:

Blue Prism Developer Documentation: Session Variables and Data Items

Blue Prism Training Material on Control Room Operations

Environmental variables are those variables that are available to all processes and business objects. So, these variables are used as dynamic variables, to make sure they can be used whenever required across the Blue Prism platform.

Understanding the Process Flow:

The process is designed to attempt the actions within Block1 up to three times before throwing an exception.

The 'Attempts' data item starts at 0 and is incremented by 1 each time the Increment Attempts Calculation stage is executed.

The 'Max Attempts' data item is set to 3, which represents the maximum number of allowed attempts.

Calculation Stage Expression:

The correct expression for incrementing the 'Attempts' data item should add 1 to the current value of 'Attempts'.

In Blue Prism, data items are referenced using square brackets. Therefore, the correct expression should be [Attempts] + 1.

Analysis of Options:

Option A: +1 is incomplete and not correct.

Option B: Attempts +1 is incorrect because it lacks the proper referencing syntax.

Option C: Max Attempts + 1 is incorrect because it references the wrong data item and will result in the incorrect calculation.

Option D: {Attempts + 1 is incorrect due to syntax issues.

Option E: [Attempts] + 1 is the correct expression, using proper syntax to reference the 'Attempts' data item.

Conclusion:

The correct expression for the 'Increment Attempts' Calculation stage is E. [Attempts] + 1.

References:

Blue Prism Developer Documentation: Calculation Stages

Blue Prism Training Material on Data Item References

In Blue Prism, certain stages can be found in both Object Studio and Process Studio. These stages are:

Read Stage (Option C): This stage is used to read data from elements and variables. It is available in both Object Studio and Process Studio.

Write Stage (Option D): This stage is used to write data to elements and variables. It is also available in both Object Studio and Process Studio.

The other stages listed in the options are specific to either Object Studio or Process Studio, but not both.

ReferencesRefer to the Blue Prism documentation and training materials which outline the stages available in Object Studio and Process Studio.