Skip to main content

Integrating an unattended RPA project with a Pega application

5 Tasks

15 mins

 Visible to: All users Applies to: Pega Robotic Automation R25
Beginner
Robotic Process Automation
English

Scenario

U+ Bank has developed a Customer Support application to process customer operations. The company division uses the BankerInsight application to keep a record of credit card transactions. As a part of the development team, your goal is to develop robotic automation that streamlines the CSR (Customer Service Representative) work by automating communication with the BankerInsight application. 

During the CSR call, the Pega application retrieves the customer data, allows the operator to select a transaction to dispute, and provide the dispute subject amount, as shown in the following figure: 

The Pega application that retrieves transactions to dispute using unattended automation. The screen contains transactions data for selected customer to choose the one to be disputed.

After submitting the transaction, the case is routed to the robotic queue according to the Case life cycle. 

The Dispute Transaction case life cycle.

Your task is to retrieve the customer ID, transaction ID, and amount to dispute, and pass the data to the robotic automation. After updating the record in the BankerInsight application, you should return the confirmation to the Pega application.  

Note: To fully handle the request from the Pega Platform the Robot Manager team needs to pick up your deployed project and assign it to the proper robot queue.

Complete the following tasks:

  • Establish a connection to the Pega Platform instance. 
  • Add the robot activity to the project. 
  • Verify the correctness of ProcessDisputedTxn automation.
  • Update the ProcessDisputedTxn automation to use the Robot Activity component properties.
  • Update the ProcessDisputedTxn automation to set the activity completion status.

The following table provides the credentials you need to complete the challenge:

User name Password
architect@ubank rules

 

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

Challenge Walkthrough

Detailed Tasks

1 Establish a connection to the Pega Platform instance

  1. Initialize and launch the Pega instance for this challenge, and then save the instance url.
  2. Download the UBank project:
  3. Save the file to your desktop and unzip the file to extract the project folder to C:\Users\<username>\Documents\Pega Robot Studio\Projects\
  4. On the Home screen in Pega Robot Studio, click Open Project, and then navigate to the projects folder and open UBank.pegaProject.
    Note: The starter project includes a configured BankerInsight application. The value of the Path field must match the location of BankerInsight on your local computer for the project to function properly. In the BankerInsight application, change the value of the Path to the location of your BankerInsight application.
  5. On the Pega Robot Studio toolbar click Tools > Options to open the Options dialog box. 
  6. In the Options dialog box, click Server connectivity.
  7. On the Server connectivity tab, in the ServerUrl field, enter your Pega instance url: https://<instanceId>.pegacea.net/prweb
    Note:
    The instanceId is an eight-characters alphanumeric value identifying your Pega training instance.
  8. On the Authentication details section, in the Username field, enter architect@ubank.
  9. In the Password field, enter rules, and then click Connect.
    Note: Depending on your system settings, you may be unable to save connection data in the CommonConfig.xml file. In that case, the connection establishment will only persist within the current session.
  10. Verify that the connection was successfully established.
    The Server connectivity dialog box with an indication that the connection to Pega instance was correctly established.
  11. In the Options dialog box, click Done.

2 Add the robot activity to the project

  1. In the Project Explorer, click and open Globals.
  2. In the Toolbox search field, enter Activity and then drag the RobotActivity component to the Globals designer.
    The RobotActivity component of the Toolbox.
  3. On the property grid of the RobotActivity, in the (Name) field, enter ProcessDisputedTxn.
  4. On the property grid of the RobotActivity, in the ActivityName field, enter ProcessDisputedTxn.
  5. On the property grid, in the ClassName enter Ubank-CustSupport-Work-DisputeTransaction.
  6. On the property grid, in the Fields property, click the more icon to open the Connect to Pega server dialog box.
    The property grid of the Robot Automation component with the more icon used to open the server connection dialg box.
  7. On the Connect to Pega server dialog box, enter the Pega instance Url and credentials provided in Task 1.
  8. On the dialog box, click Get fields to open the Select fields dialog box.
    The Connect to Pega server dialog box with the Get fields button.
  9. On the Select fields dialog box, select Customer No, Transaction Amount, and Transaction ID to dispute, and then click Submit (3).
  10. On the Toolbar, click Save.

3 Verify the correctness of ProcessDisputedTxn automation

  1. In the Project Explorer, click and open ProcessDisputedTxn automation.
  2. In the upper-right corner of Pega Robot Studio, click Test to verify the starting project interface.
  3. In the testing automation dialog box, enter the following values:
    1. customerNo: 1234500078963456
    2. transactionId: 2535
    3. txnAmount: 10
      The testing automation dialog box with the test parameters.
  4. In the Testing automation dialog box, click Test to start the automation test.
  5. Verify the dispute status for the transaction in BankerInsigh application is Success, and then close the BankerInsight application.
  6. Verify that the dispute has been added to the BankerInsight application with correct data, and that the confirmation dialog box is displayed.
  7. In the Test complete dialog box, click Done to finish the automation testing.

4 Update the ProcessDisputedTxn automation to use the Robot Activity component properties

  1. In the Project Explorer, click and open ProcessDisputedTxn automation.
  2. On the automation surface, click and select the automation Entry Point, right-click, and then select Delete.
    Removing an Entry Point from the automation surface.
  3. In the dialog box, click Yes to confirm an entry point removal.
  4. On the Palette, in the Globals section, drag the ProcessDisputedTxn component to the automation surface to open a Select Action dialog box.
  5. In the Select Action dialog box, select the Activity Started event, and then click Add.
  6. On the Palette, in the Globals section, drag the ProcessDisputedTxn to the automation surface again.
  7. In the Select action dialog box, click More, and then open the Property tab.
  8. In the Property tab, select Customer_No property, and then click Add (1).
    The Select action dialog box presenting the properties assigned to the Robot Activity.
  9. Connect the design blocks on the automation surface as shown in the following figure, to source the input data for the CustomerSearch method from the robot activity:
    The connections on the automation surface to assign the property as an input parameter.
  10. Drag the ProcessDisputedTxn component to the automation surface to open the Select action dialog box.
  11. In the Property tab, select transaction_Amount, and Transaction_ID_to_dispute properties, and then click Add (2).
    Adding two properties from the Select action dialog box.
  12. Connect the design blocks on the automation surface as shown in the following figure, to source the input data for the AddTransactionAsDispute automation from the robot activity:
    Automation surface with design block representing the added parameters.
  13. Drag the ProcessDisputedTxn component to the automation surface to open the Select action dialog box.
  14. In the Property tab, select Customer_No, and Transaction_ID_to_dispute properties, and then click Add (2).
  15. Connect the design blocks on the automation surface as shown in the following figure, to source the input data for the SendDisputeConfirmation automation from the robot activity:
    The automation surface with the data connection established for newly added parameters.
  16. On the toolbar, click Save to save the automation.

5 Update the ProcessDisputedTxn automation to set the activity completion status

  1. Drag the ProcessDisputedTxn component to the automation surface to open the Select action dialog box.
  2. Click the Method tab, select the SetCompletionStatus method, and then click Add.
    The Select action dialog box presenting methods for the robot activity.
  3. In the SetCompletionStatus method, set the status field to CompletedWithErrors.
  4. On the automation surface, delete the ShowMessage method of MessageManifest and the JumpToExit design block connected to it. 
  5. On the Toolbox tab, in the search field, enter GetMessage, and then drag the GetMessage method to the automation surface.
  6. On the automation surface, connect design blocks as shown in the following figure:
    The automation surface showing connections for the SetCompletionStatus method.
  7. Drag the ProcessDisputedTxn component to the automation surface to open the Select action dialog box.
  8. Click the Method tab, select the SetCompletionStatus method, and then click Add.
  9. In the SetCompletionStatus design block, select the status field to completed.
  10. On the automation surface, connect design blocks as shown in the following figure:
    The automation surface with all block connected.
  11. On the toolbar, click Save to save the automation.

This Challenge is to practice what you learned in the following Module:

Available in the following mission:

Return to mission
If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice