Upgrading to Pega Robot Manager 6 for Pega Platform 7.4
Upgrade to Pega Robot Manager™ 6 on Pega Platform™ 7.4 to take advantage of new features such as instant email notification in case of issues, ability to start, stop, terminate and schedule robots from the Pega Robot Manager interface. For a complete list of new features, see Pega Robot Manager 6.
- Back up your application files, and Pega Platform, in case you need to restore your system.
- Make sure that you are using Pega version 8.0 SP1 2019 or later of Pega Robotic Automation™.
- Install Pega Platform 7.4, and then verify your installation as described in the Platform Installation Guide for your environment, available on the Deployment guides page.
- Apply the following hotfixes:
For more information, see Obtaining hotfix packages.
- If you previously customized dynamic system settings related to Pega Robot Manager, note them down so that you can restore them after upgrading. To view the current dynamic system settings, perform the following actions:
- In Designer Studio, click Records > SysAdmin > Dynamic System Settings.
- Filter by Owning Ruleset Pega-Robotic-AutomationPackageManagement.
To upgrade to Pega Robot Manager 6, perform the following steps:
- Download Pega Robot Manager 6 from the Pega Robot Manager Exchange page.
- Extract the files from the PegaRobotManager.zip file.
- Import the Pega Robot Manager application bundle into Pega Platform:
- Log in to Pega Platform (
https://<hostname>:<port>/prweb) by using the administrator ID that you set up when you installed Pega Platform (for example, email@example.com) and the password that you specified.
- Open the Import Wizard by clicking Designer Studio > Application > Distribution > Import.
- Depending on your browser, click Choose file or Browse, browse to the location where you extracted the PegaRobotManager.zip file, open the 7.4\Rules\PegaRobotManager_V6_74.jar file, and then click .
- Select Enable advanced mode to provide more granular control over the import process, and then click .
- To preserve existing operators, do not select the Enable new operators and overwrite existing operators on import check box.
- Click and finish the upgrade process.
- If you are upgrading Robot Manager from releases earlier than version 5, run the pxMigrateRobotLogEntriesToV5 activity to upgrade rendering of the following pages and widgets:
Perform the following actions:
- Robots > Work groups and Robots > Robots pages (Previously located under Work groups and Users > Robots)
- The page that is displayed when you click a robot
- The page that is displayed when you click an assignment type
- The Robot status and Automation alerts over time widgets
- In Designer Studio, search for pxMigrateRobotLogEntriesToV5.
- In the search results, click the pxMigrateRobotLogEntriesToV5 activity to open it.
- Click Actions > Run.
Depending on the volume of historical robotic process automation audit data in your database, this activity might take some time to complete.
Adding Pega Robot Manager to an existing application that uses a UIKit version earlier than 11.01
If you have an existing Pega Platform application that uses a version of the UIKit earlier than 11.01 , you can add Pega Robot Manager to your application by completing the following steps:
- Open the PegaRoboticAutomationConsole application rule:
- Click Records.
- Click Application Definition > Application.
- Search for PegaRoboticAutomationConsole by using the Name filter.
- Click PegaRoboticAutomationConsole.
- In the header, click Definition.
- In the Edit Application form, in the Built on application(s) section, add UIKit 11.01 to the application stack.
- Click Add application.
- In the Name field, press the Down Arrow key and select UIKit.
- In the Version field, press the Down Arrow key and select 11.01.
- Add your application to the application stack.
- Click Add application.
- In the Name field, press the Down Arrow key and select the name of your application.
- In the Version field, press the Down Arrow key and select the version of your application.
- Click .
- Create an access group that points to the PegaRobotAutomationConsole application:
- Click .
- Enter a name and description, and then click Create and Open.
- In the Application section, in the field, enter PegaRoboticAutomationConsole.
- In the Version field, enter 02.02.01.
- In the Available portals section of the access group, add pyRoboticConsole to the list of portals.
- On the Advanced tab of the access group, add the default work pool of your existing built-on application.
- Click in the Edit Access Group form.
- Assign the new access group to your users. For more information, see Profile tab on the Operator ID form.
Changes to dynamic system settings
The default setting for WorkgroupSpecifiedInPayloadTakesPrecedence dynamic system setting was changed from "true" to "false".
The following dynamic system settings were added in Robot Manager 6:
- AllowedWaitTimeForRobotRegistration - specifies the maximum expected time that the RPA Service should take to start up the robot runtime system. It includes the time to unlock the remote machine, and start the runtime process. Default value: 120 seconds.
- MaxStartsIssuedPerScheduleAction - prevents Pega Robot Manager from continuously attempting to restart a robot that has failed to start during one Scheduled action or Otherwise event. Robot Manager will check this value before attempting to start a robot. If the number of start attempts is less than the number provided, the start will be issued. Default value: 4
- ServiceOperatorHeartbeatInterval - defines how often the RPA Service should send a heartbeat signal to Pega Robot Manager. When the RPA Service does not send a heartbeat within this interval, it is assumed to be not running. When the RPA Service is not running, UI options (such as Start a robot and Terminate a robot) are not available from Pega Robot Manager. Default value: 45 seconds.
- TimeoutIntervalForRobotCommandToBeCompleted - determines the time-out interval for the start command issued to robots in conjunction with the RPA Service heartbeat interval. Default value: 30 seconds.
Changes to decision tables
The following decision tables were added in Robot Manager 6:
Changes to agents
The following Agents were added in Robot Manager 6:
Changes to pyCompleteAutomation flow action
In previous versions of Robot Manager, the pyCompleteAutomation flow action had no default behavior defined, and it was not marked as an Extension. In Robot Manager 6, this flow action is marked as an Extension, and its default behavior is to consider the automation status as "Complete" and move the flow to the next stage of the case life cycle.
It is strongly recommended to customize the default behavior of pyCompleteAutomation flow action to better suit the needs of your organization.
Configuring email notifications
Pega Robot Manager 6 supports notifying users by email in case of unexpected behavior or errors. To use this feature, perform the following steps:
- Configure an email account that will be used to send the notifications. For more information, see Creating an email account.
- Set the Public Link URL to the following format:
http://<host>/prweb/PRServlet. For more information, see System Settings – Resource URLs tab.
What to do next
For further technical details about Pega Robot Manager 6, see Configuring Pega Robot Manager 6.
Published January 16, 2019 — Updated February 18, 2019