PEGACPRSA22V1 Questions and Answers

This question is about understanding how a For Loop interacts with a Data Grid View (dgv) control, specifically using the GetCellValue method in Pega Robot Studio automations.

Automation Analysis

Let’s break down the logic step by step:

1. Transaction History Table (Data Grid)

Row Index

Txn ID

Date

Description

Amount

0

3255

05/05/2014

Cash deposit

100

1

1763

05/22/2014

NSF Grocery

-123.38

2

3451

06/01/2014

Deposit

200

3

2535

07/05/2014

Gas

-39.57

4

3358

07/15/2014

Cash deposit

50

2. For Loop Configuration

Initial: 0

Increment: 1

Limit: 3

→ The loop will execute for Index values 0, 1, and 2 (because the limit is exclusive at 3).

3. GetCellValue Method

The GetCellValue method retrieves a value from the Data Grid View (dgvAcctTrans) control.

It uses two input parameters:

Row → the row index (connected from For Loop Index)

Column → the column index (hard-coded as 0)

In the automation, the column value is explicitly set to 0, meaning it will always retrieve the Txn ID column.

4. Execution Order

Iteration

Row Index

Column (0 = Txn ID)

Retrieved Value

Output (MessageBox)

1

0

0

3255

MessageBox shows 3255

2

1

0

1763

MessageBox shows 1763

3

2

0

3451

MessageBox shows 3451

5. Output Sequence

The MessageBox displays three transaction IDs in order:

3255, 1763, 3451

Conclusion

The GetCellValue retrieves only the first column (Txn ID) for rows 0 to 2.

Thus, the automation will display the transaction IDs sequentially in three message boxes.

Correct Answer: A. 3255, 1763, 3451

Comprehensive Extract from Pega Robotics Documentation:

From Pega Robotics System Design and Implementation Guide, section “Using Data Grid View Controls in Automations”:

“The GetCellValue method retrieves the value at a specified row and column index of a DataGridView control.

When used in conjunction with a ForLoop component, the row parameter is typically connected to the ForLoop’s Index output.

The loop executes from the defined Initial value to one less than the Limit value, retrieving sequential cell values for each iteration.”

Detailed Reasoning Recap:

ForLoop Index runs: 0, 1, 2

GetCellValue(row, 0) retrieves column 0 (Txn ID) for each row.

MessageBox displays results sequentially.

Final Answer: A. 3255, 1763, 3451

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

In Pega Robot Studio, the DataTableProxy component acts as an intermediary between automations and a Data Table, allowing the automation to read, manipulate, and update tabular data stored in the project.

When you drag an element such as a DataTableProxy from the Globals section of the Palette onto the automation design surface, Pega Robot Studio presents the user with available actions (methods, properties, or events) that can be executed using that component. This is done through a Select Action dialog box, which lists all available methods associated with the DataTableProxy (e.g., GetTable, AddRow, RemoveRow, Find, Update, etc.).

From the Pega Robotics System Design and Implementation Guide (Data Table Proxy and Data Handling section):

“When a component such as a DataTableProxy or connector object is dragged from the Palette onto the automation design surface, the system opens the Select Action dialog box.

This dialog lists all available methods and properties of the selected object, allowing the developer to select the action to instantiate on the automation surface.

The dialog ensures developers can directly add the desired operation (such as GetTable or UpdateRow) without manually searching through the object’s members.”

Detailed Reasoning:

The DataTableProxy represents a data-handling object; it does not directly add a “property” or “method” by default when dragged.

Instead, Robot Studio prompts you with a Select Action dialog box, allowing you to choose which specific method (like GetTable, FindRow, or AddRow) you want to include in your automation.

After the selection is made, the chosen method (for example, GetTable) is then displayed on the automation surface.

Option Analysis:

A. Incorrect — A property is not automatically added; you must choose an action first.

B. Incorrect — The Quick Add dialog is used for linking variables and not for proxy components.

C. Incorrect — A “proxy design block” is not automatically added without specifying a method.

D. Correct — The Select Action dialog box opens to let you choose the method or property to add.

E. Incorrect — GetTable may be one of the options available, but it is not added automatically.

Hence, the correct answer is D — dragging a DataTableProxy from the Globals section triggers the Select Action dialog box to open, allowing the developer to choose which action to use.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

In Pega Robot Studio, the Start My Day (SMD) functionality allows a user to define and launch all required applications at once when starting work. The configuration of these applications is performed in the Manage Applications window, where each application can be individually enabled or disabled for automatic startup.

According to the Pega Robotics System Design and Implementation Guide, in the section “Start My Day Configuration and Manage Applications”, the documentation specifies the following:

“Applications configured for Start My Day will launch automatically when the Start My Day feature is invoked.

The Manage Applications dialog lists all project applications and determines which ones are launched using the ‘Enabled’ checkbox.

Only applications marked as enabled will be started when the user initiates Start My Day. Applications that are listed but not enabled remain closed.”

The screenshot in the question shows the following configuration under the Manage Applications window:

Application

Enabled

Type

Path

Pega Finance

Yes

Adapter

C:\Users\Pega Training\Desktop\BankerInsight...

BankerInsight

Yes

Adapter

C:\Program Files (x86)\CRM Setup\CRM.exe

CRM

No

Exe

C:\Program Files (x86)\CRM Setup\CRM.exe

Notepad

Yes

Exe

C:\Windows\notepad.exe

From this configuration, the Enabled column indicates that the following applications will start automatically when Start My Day is triggered:

Pega Finance

BankerInsight

Notepad

The CRM application is not enabled and therefore will not launch.

Option Analysis:

Option A (Pega Finance, Notepad, BankerInsight): Correct, as these are the enabled applications.

Option B (CRM, BankerInsight): Incorrect, because CRM is not enabled.

Option C (CRM, Notepad, BankerInsight): Incorrect, because CRM is not enabled.

Option D (Pega Finance, CRM, Notepad, BankerInsight): Incorrect, because CRM is not enabled.

Therefore, the correct answer is A. Pega Finance, Notepad, BankerInsight.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

The Label/Jump To functionality in Pega Robot Studio is used to improve automation organization and logical control flow.

Labels act as named anchor points within a single automation, and Jump To links can redirect the execution flow to these labeled points.

According to the Pega Robotics System Design and Implementation Guide, section “Using Labels and Jump To Blocks in Automations”:

“The Label/Jump To functionality enables structured flow management within a single automation.

Labels define points in the automation to which the execution flow can jump.

Jump To blocks redirect execution to a corresponding label, allowing developers to organize complex automations into manageable sections.

This feature is particularly useful for debugging, error handling, and implementing multiple exit paths within a single automation.”

Detailed Reasoning:

A. It allows you to pass variables to different parts or workflows of the same automation.

Incorrect. The Label/Jump To mechanism changes the flow of execution; it does not pass or transfer variable data between workflows.

B. It allows you to keep automations organized and aids in debugging.

Correct. Labels and Jump To blocks make complex automations more readable and structured by dividing logic into sections. This improves debugging and maintenance.

C. It allows you to pass variables to different automations of the same project.

Incorrect. Variables between automations are passed using parameters (inputs/outputs), not Label/Jump To blocks.

D. It allows you to have multiple Exit points in an automation.

Correct. By strategically placing labels and jumps, you can create multiple exit conditions or termination points within a single automation, improving control flow.

E. It allows you to connect with other automations in the project.

Incorrect. Connections to other automations are made through automation calls, not Label/Jump To links.

Final Correct Answer: B, D

Reference http://help.openspan.com/80/Platform_Configuration/RuntimeConfigXML.htm

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

The Excel Connector in Pega Robot Studio is a lightweight component that provides direct interaction with Excel files without relying on the Microsoft Excel application. It is ideal for background processing, where users are not required to interact with Excel directly.

According to the Pega Robotics System Design and Implementation Guide (Excel Integration and Connectors section):

“The Excel Connector allows automations to open, read, and modify Excel workbooks without requiring Microsoft Excel to be installed.

It operates directly on the file system level, supporting operations such as reading or writing to specific cells, entire worksheets, or data ranges.

The connector does not use Excel Interop; therefore, no interrogation or Excel application process is necessary.”

Explanation of Options:

A. Correct — The Excel Connector supports data range operations such as defining, reading, or writing to specific sets of cells within a worksheet.

B. Incorrect — The connector does not depend on any installed version of Microsoft Office; it functions independently.

C. Incorrect — Interrogation applies to UI applications, not file-based connectors like Excel Connector.

D. Correct — The connector works without Excel being installed; it manipulates workbook data directly through file handling APIs.

E. Incorrect — When user interaction with Excel is required, Excel Interop (Excel Application Connector) should be used instead of the file-based Excel Connector.

Therefore, the correct statements are A and D.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

In Pega Robot Studio, toast notifications are used to display short, non-blocking messages to users during runtime. These notifications are highly customizable and can be globally managed to maintain consistent branding across an enterprise automation project.

According to the Pega Robotics System Design and Implementation Guide (UI Messaging and Toast Notifications section):

“Toast notifications can be added to the Globals tab of a project to maintain consistent visual and behavioral configuration throughout the solution.

The notification element placed in Globals allows setting properties such as title, duration, color, font, and position that are shared by all automations calling the Show() method.

Automations reference the global toast notification by invoking its Show method from the Globals section of the Palette.”

This means that:

The best practice for ensuring uniform design and branding (consistent colors, layout, font, and position) for toast messages is to define one global toast notification in the Globals tab.

Once the global toast notification is configured, all automations that require displaying toast messages will simply call its Show() method, inheriting the standardized display settings.

Option Analysis:

A. Incorrect — Adjusting the Utilities section does not define reusable toast notifications.

B. Incorrect — The project properties do not include toast formatting controls.

C. Incorrect — Creating an automation to set these dynamically would not enforce consistent styling across all notifications and is not recommended.

D. Correct — Placing a toast notification in the Globals tab allows defining display parameters once and reusing them via the Show() method in automations, ensuring global consistency in branding and formatting.

Therefore, the correct and Pega-recommended approach is Option D.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

The PegaRuntimeConfig.xml file contains configuration settings that control how users interact with Pega Robot Runtime on their desktops.

These settings define parameters such as:

Robot tray icon visibility

Notification preferences

Runtime startup behavior

Access permissions for attended automation

According to the Pega Robotics System Design and Implementation Guide, section “Runtime Configuration Settings”:

“The PegaRuntimeConfig.xml file defines user interaction settings and behavior of Pega Robot Runtime on end-user desktops.

It specifies configurations related to user access, tray icon visibility, notification pop-ups, and desktop automation permissions.”

Detailed Reasoning:

A. PegaConfig.xml – Not a valid configuration file in Pega Robotics.

B. CommonConfig.xml – Used for shared system-wide connectivity and Robot Manager settings.

C. PegaStudioConfig.xml – Stores configuration data for Pega Robot Studio (developer-specific).

D. PegaRuntimeConfig.xml – Correct. Defines desktop-level user interaction and Runtime behavior.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

When deploying robotic solutions to Pega Robot Manager, the connection and authentication details — such as Robot Manager server URL, authentication mode, and registration configuration — are stored in the file CommonConfig.xml.

This configuration file is shared between both Pega Robot Studio and Pega Robot Runtime, ensuring that both use consistent connectivity settings.

According to the Pega Robotics System Design and Implementation Guide, section “Pega Robot Manager Integration and Configuration Files”:

“The CommonConfig.xml file contains shared configuration information that is used by both Pega Robot Studio and Pega Robot Runtime.

It includes global settings such as:

Connection information for Pega Robot Manager (URL, ports, authentication)

Deployment configuration values

Environment registration and runtime connectivity settings.

PegaRuntimeConfig.xml and PegaStudioConfig.xml are used for local settings only, while CommonConfig.xml stores the Robot Manager connection configuration used during deployment.”

Detailed Reasoning:

A. PegaStudioConfig.xml – Used for developer-specific configuration within Robot Studio, not for deployment or server settings.

B. CommonConfig.xml – Correct. This file contains the Robot Manager connectivity configuration and shared settings.

C. PegaRuntimeConfig.xml – Controls runtime behavior on client machines, not Robot Manager connections.

D. PegaConfig.xml – Not a valid configuration file in Pega Robotics.

(Correct Order):

Hover your pointer over the control.

Click the Gear icon.

Set the Action to Set Text.

In the Value list, select Create New.

Set the Value source to Input parameter.

In the Name field, enter the name of the input parameter.

Click Submit to save the input parameter.

Click Save to save the step.

Targeted Step Creation is a Pega Robot Studio feature used to record automation steps directly by interacting with an interrogated control (for example, typing into a textbox). When the automation being recorded needs to receive data from another automation, an input parameter is configured as the value source for the recorded step.

According to the Pega Robotics System Design and Implementation Guide, section “Recording Steps and Configuring Input Parameters”:

“When recording a targeted step for an input control:

Hover over the target control and select the Gear icon to open the recording configuration.

Choose the appropriate action (for example, Set Text for text boxes).

Create a new value reference and select Input parameter as the value source.

Assign a name to the input parameter that will be passed from the calling automation.

Submit and save the step to finalize the recording.”

Detailed Step Reasoning:

Hover your pointer over the control.

This initializes the control recognition in targeted step creation mode.

Click the Gear icon.

Opens the step configuration dialog for the selected control.

Set the Action to Set Text.

Defines the intended action for the control (entering text).

In the Value list, select Create New.

Creates a new value definition to assign data to the control.

Set the Value source to Input parameter.

Ensures that the value for the text input will come from an external automation that invokes this one.

In the Name field, enter the name of the input parameter.

Defines the name of the input variable so that it can be referenced when calling this automation.

Click Submit to save the input parameter.

Confirms and stores the parameter definition.

Click Save to save the step.

Finalizes the recorded step in the automation sequence.

Final Ordered Steps:

Hover your pointer over the control.

Click the Gear icon.

Set the Action to Set Text.

In the Value list, select Create New.

Set the Value source to Input parameter.

In the Name field, enter the name of the input parameter.

Click Submit to save the input parameter.

Click Save to save the step.

Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

During interrogation of web applications, developers often encounter dynamic or hidden controls — such as drop-down menus or hover-triggered lists — that do not immediately appear on the page.

To successfully interrogate these elements, Pega Robot Studio provides two essential tools:

The Delay option on the Interrogation Form, which allows the developer time to trigger the hidden control before capture.

The Select Element option, which enables precise selection of an element directly from the DOM, even if it is not immediately visible.

According to the Pega Robotics System Design and Implementation Guide, section “Interrogating Dynamic and Hidden Web Controls”:

“When interrogating hidden or dynamically rendered controls:

Use the Delay option on the Interrogation Form to give yourself time to hover over or activate a hidden control before Robot Studio attempts to capture it.

Use the Select Element option to manually highlight and select a control from the web application’s DOM, even when it is displayed only after an interaction such as mouse hover.These methods are particularly effective for controls that expand or render asynchronously, such as drop-down menus or tooltip-triggered elements.”

Detailed Step Reasoning:

C. Use the Delay option on the Interrogation Form.

Correct.

The Delay setting pauses the interrogation process for a specified number of seconds, allowing you to hover over the hidden element (e.g., AddressType menu) and make it visible before capture.

Once the menu appears, Pega Robot Studio can detect and interrogate it.

D. On the Interrogation Form, select Select Element.

Correct.

The Select Element tool allows manual selection of an element directly from the web page’s HTML DOM structure.

This is especially useful for hidden or dynamically rendered elements like the AddressType dropdown that may not be visible until hovered over.

Incorrect Options Explained:

A. In the Interrogation Form dialog box, select HTML Table Editor.

Incorrect.

The HTML Table Editor is used to inspect and modify HTML table-based controls (grid or table structures), not dynamic menus.

B. On the Web Controls tab, select the page, and then click List Web Controls.

Incorrect.

The List Web Controls option lists already recognized controls in the DOM but cannot reveal or capture hidden dynamic elements.

E. On the Application tab, click the Virtual Controls tab.

Incorrect.

Virtual Controls are used for defining custom controls when the default adapter cannot identify one, not for capturing hidden menu elements.

Final Correct Answer:

C. Use the Delay option on the Interrogation Form.

D. On the Interrogation Form, select Select Element.

In Pega Robot Studio, an environment override allows developers to configure multiple deployment environments (such as test, staging, and production) using a single project. This helps you avoid creating separate projects for each environment and ensures consistent automation logic while dynamically switching between environment-specific settings at runtime.

According to the Pega Robotics System Design and Implementation Guide, section “Managing Environment Overrides and Multi-Environment Deployments”:

“Environment overrides provide a mechanism to define environment-specific configuration values for applications within a project.

For example, the same automation logic can be used for both test and production systems by creating separate environment override files — one for the test environment and one for the production environment — each specifying unique paths, credentials, or URLs for the corresponding system.”

Detailed Reasoning:

The HR system has different access points for test and production, which typically means different URLs or executable paths.

The automation logic (how the robot interacts with the HR application) remains identical; only the connection configuration changes.

Therefore, instead of creating multiple applications or modifying logic, you configure two environment override files — one for production and one for test — each defining environment-specific details such as:

Application path (for Windows adapters)

StartPage URL (for web adapters)

Credentials or runtime parameters

This allows a single automation project to adapt dynamically based on which environment override is active during deployment or testing.

Option Analysis:

A. Incorrect — A single override cannot contain two sets of environment details; each override corresponds to one environment.

B. Incorrect — Creating two applications increases complexity and redundancy; both would duplicate the same logic.

C. Incorrect — Adding both separate applications and overrides is unnecessary; overrides alone are sufficient for environment flexibility.

D. Correct — Two environment overrides (one for production, one for test) allow the same project and automation logic to function properly across both environments.

Therefore, the correct answer is D. Create two environment overrides for the HR System project: one override for production, and one for test.

In Pega Platform, different integration points exist to trigger robotic automations (either desktop or unattended) through Pega Robot Studio. Each serves a specific purpose depending on whether the automation retrieves data, runs as part of a user interaction, or executes through background processing.

According to the Pega Robotics System Design and Implementation Guide, section “Integration Points Between Pega Platform and Robotic Automations”, the following definitions are provided:

Data Pages:

“A Data Page can be configured with a Robotic Desktop Automation (RDA) data source.

This allows the case to call a robotic automation to retrieve or send data between the Pega Platform and an external system.

The automation runs in the background to provide data enrichment or lookup functions.”

Flow Actions:

“Flow actions can invoke robotic desktop automations before or after a case step executes.

They enable synchronous automation interaction as part of a user’s workflow in Pega Platform.”

Robot Queues:

“A Robot Queue contains assignments that are sent to unattended robots for background processing.

One or more robots pick assignments from the queue and execute the configured automations associated with those cases.”

Detailed Reasoning:

Data Pages → Used to source or update data automatically from external systems by triggering a Robotic Desktop Automation (RDA) or Robotic Process Automation (RPA).

Hence, it “sources application data from Pega Platform applications by calling automations.”

Flow Action → Used within a case to trigger RDA automations either before or after a step.

Hence, it “calls automations to run before or after completing a step.”

Robot Queue → Used by unattended robots managed through Robot Manager to fetch assignments and perform automations.

Hence, it is the process by which “one or more robots access the case assignment to perform the automations.”

Final Correct Matching Order:

Term

Description

Data pages

Source application data from Pega Platform applications by calling automations.

Flow action

Within the case, it calls automations to run before or after completing a step.

Robot queue

One or more robots access the case assignment to perform the automations.

 Retrieves the assignment from the queue.

 Obtains the case data that is associated with the assignment.

 Performs the specified automation task.

 Sends the updated data, the assignment, and confirmation back to the case.

 Retrieves the next assignment from the queue.

Unattended automations (also known as Robotic Process Automation (RPA)) are designed to work without human intervention. These automations process assignments or cases that are queued by Pega Platform and retrieved by robots through the Pega Robot Manager service.

According to the Pega Robotics System Design and Implementation Guide, in the section “Unattended Automation Workflow and Queue Processing”, the following sequence defines how an unattended robot processes a work item:

“1. The robot retrieves an assignment from the work queue managed by Pega Robot Manager.

2. The robot then requests the case data associated with the assignment, which contains the necessary contextual information.

3. The robot performs the defined automation tasks within the target applications using the case data as input.

4. Upon completion, the robot updates the case, returns the assignment results, and confirms the completion to Pega Platform.

5. The robot then retrieves the next available assignment from the queue to continue processing.”

Detailed Step Reasoning:

Retrieves the assignment from the queue — The robot begins by pulling a new assignment from the Pega Platform work queue through the Robot Manager interface.

Obtains the case data that is associated with the assignment — After assignment retrieval, the robot obtains the case data (for example, customer details or transaction info) from the platform.

Performs the specified automation task — The robot executes the defined automation using the fetched data, interacting with the necessary enterprise applications.

Sends the updated data, the assignment, and confirmation back to the case — Once the task is complete, the robot posts the results and completion confirmation back to Pega Platform.

Retrieves the next assignment from the queue — The cycle repeats as the robot moves to the next queued case or assignment.

This structured loop ensures consistent, unattended case handling by robotic workers, maintaining synchronization between Pega Platform and the robotic runtime environment.

Final Correct Order:

Retrieves the assignment from the queue.

Obtains the case data that is associated with the assignment.

Performs the specified automation task.

Sends the updated data, the assignment, and confirmation back to the case.

Retrieves the next assignment from the queue.