LinkedIn
Copied!

Table of Contents

Enabling Workforce Intelligence for Pega Attended RPA clients

If you are already running attended automations, adding Workforce Intelligence can help you identify additional automation opportunities and process inefficiencies. 

You have two options for how you approach adding Workforce Intelligence. Before you enable Workforce Intelligence, decide which of the following options is best for you:

Option 1: Keep your existing Robotic Automation package and update the package to include the Workforce Intelligence settings.
Option 2: Create a separate package for Workforce Intelligence to use with your Robotic Automation package.  

After deciding your approach, enable Workforce Intelligence by completing the following tasks:

Updating the CommonConfig.xml file  

The CommonConfig.xml file must have the correct Robotic Process Automation and Workforce Intelligence parameters when enabling Workforce Intelligence. Because you are currently running attended robots, the Robotic Process Automation information in this file is already configured and you only need to update the Workforce Intelligence information.

Complete the following steps to enable the connection from Robot Runtime to Workforce Intelligence in the CommonConfig.xml file.

  1. In the \ProgramData\Pegasystems folder, open the CommonConfig.xml file in a text editor.  
  2. Locate the Server name=Intelligence entry in the file. 
  3. Verify that the baseURL attribute follows the correct format of https://xxx.wfi.pega.com where xxx is your organization’s Workforce Intelligence portal.
  4. Change the enabled key to true, as in the following example:
    ​​​​​​

    <ServerConfiguration tenant="TenantName">  

    <Servers>  

    <Server name="RobotManager" baseURL="https://MyPegaServer.com/prweb" enabled="false" proxyAddress="" RPA="false" suppressNotificationsForRPA="false" authenticationType="Basic" RPAServiceOperator="RPAOperator" workgroup="" robotName="{MachineName}"/>  

    <Server name="Config" baseURL="https://omc.openspan.com/" enabled="false" proxyAddress=""/>  

    <Server name="Intelligence" baseURL="https://xxx.wfi.pega.com" enabled="true"proxyAddress="" />  

    <Server name="IdP" baseURL="https://MyAuthServer.com/Endpoint" enabled="false" proxyAddress=""/>  

    <Server name="CredentialManager" enabled="false" baseURL="" mappingFileLocation="CommonApplicationData" providerType="DPAPI" />  

    <Server name="PegaDevServer" baseURL="" enabled="false" proxyAddress="" authenticationType="" />  

    </Servers>  

    </ServerConfiguration> 

If you have enabled OAuth and added the required parameter to the CommonConfig.xml file, then an additional wfiOauthEnabled="true" parameter is displayed in the Intelligence section.  

Updating the Robot Runtime configuration 

For the Robot Runtime configuration, setting the AllowRunWithNoPackage key to true is critical when enabling Workforce Intelligence. The Workforce Intelligence data collectors (Runtime users) do not need a robotic automation package. Allowing Robot Runtime to run without a package ensures that Robot Runtime starts in the background without generating any error messages for your data collectors. 

If you have Robot Manager, update the key in Robot Manager instead of in the RuntimeConfig.xml file. 

Update the AllowRunNoPackage key in the RuntimeConfig.xml file

If you do not have Robot Manager, update the AllowRunNoPackage key in the RuntimeConfig.xml file.  

  1.  If the RuntimeConfig.xml file is present within a user’s profile, such as in C:\Users\{username}\AppData\Roaming\Pegasystems or %appdata%/pegasystems, delete this file so that updated configuration is copied from the installation folder to this location. 
  2. Navigate to your installation folder, based on your environment:
  • 64-bit environmentC:\Program Files (x86)\Pegasystems\Pega Robot Runtime
  • 32-bit environmentC:\Program files\Pegasystems\Pega Robot Runtime
  1. Open the RuntimeConfig.xml file.
  2. Change the AllowRunWithNoPackage key to true, as shown in the following example. 

    <add key="AllowRunWithNoPackage" value="true"/>    

Update the AllowRunNoPackage key in Robot Manager

If you have Robot Manager, update the AllowRunWithNoPackage key value to true within Robot Manager. Refer to Managing Runtime Configuration Files for additional information. 

Based on your current setup of Pega Attended RPA, such as whether you are using Robot Manager or the network share folder to run automations, the deployment  of the RuntimeConfig.xml file might change.  
AllowRunWithNoPackage key in Robot Manager
AllowRunWithNoPackage key in Robot Manager
AllowRunWithNoPackage key in Robot Manager

Deploying the DesktopAnalyticsConfig.xml file

This task is only required if you are using Robot Runtime 19.1.76 or earlier. Robot Runtime 19.1.77 and later supports a synchronization feature that updates the DesktopAnalyticsConfig.xml file after a configured refresh interval, which is usually 15 minutes.

The DesktopAnalyticsConfig.xml file directs Robot Runtime to start the data collection for Workforce Intelligence. The Workforce Intelligence Service Delivery team can provide a DesktopAnalyticsConfig.xml file where the data collection is turned off by default, if needed. However, if data collection is turned on in the file, then you need to deploy this file for data collection to begin. 

  1. Obtain the DesktopAnalyticsConfig.xml file from the Workforce Intelligence Service Delivery Team if you do not already have it.
  2. Deploy the file as a part of your Robot Runtime software package to one of the following locations, depending on your environment.
  • 64-bit environmentC:\Program Files (x86)\Pegasystems\Pega Robot Runtime
  • 32-bit environmentC:\Program files\Pegasystems\Pega Robot Runtime  

 Data collection tips 

After successfully adding Workforce Intelligence, keep the following tips in mind for managing data collection. 

  • You can manage data collection from the Workforce Intelligence portal using the Client Configuration page and Organization page.   
  • Data collection is only enabled for data collectors who are part of a team within the hierarchy.   
  • Data collection is disabled by default for the Unknown team.   
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.