Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Defining multiple portals for Workforce Intelligence in Robot Runtime

Updated on May 27, 2022

Some organizations use multiple Workforce Intelligence portals. For example, customer service data might be on a different portal from sales data. To simplify managing multiple portals, your desktop software deployment team can add portal URLs to a urlOptions attribute in the CommonConfig.xml file.

Defining this attribute enables Pega Robot Runtime to match a data collector (associate) to the correct portal URL, based on where the data collector is active. The urlOptions attribute is particularly useful when data collectors move from one team to another, and the teams are on different portals. 

Important: The urlOptions attribute is available in Robot Runtime version 19.1.108 and later. 
  1. In the CommonConfig.xml file, in the Servers section, locate the entry for the Intelligence server.
  2. Locate the baseURL attribute, and ensure that the value for this attribute is empty.

Note: Do not delete the baseURL attribute. When you use the urlOptions attribute, Robot Runtime does not reference the baseURL attribute. However, baseURL is a required attribute in the CommonConfig.xml file.  
  1. Add the urlOptions attribute, and enter the URL for each portal, separated by commas.

    <Server name="Intelligence" baseURL="" enabled="True" proxyAddress="" wfiOauthEnabled="true" urlOptions=","/>
Note: The purpose of this example is to show the baseURL and urlOptions attributes. Your Intelligence server section might include or exclude other attributes, based on your configuration. For example, wfiOauthEnabled="true" is an optional attribute and it is only required if your organization uses Runtime OAuth. 
  1. Save and close the file. 

Result: The changes take effect after the DesktopAnalyticsConfig.xml file refreshes, which takes 15 minutes by default. Robot Runtime checks the URLs in order, starting with the first URL listed for the urlOptions attribute. During this check, Robot Runtime sends data to the first URL where the data collector is active.

Multiple portals FAQ

What happens when a data collector is active on one portal for a few hours and then moved to another portal for the rest of the day?

After the DesktopAnalyticsConfig.xml file refreshes, Robot Runtime sends data to the first portal where the data collector is currently active.

Note: When moving a data collector, administrators need to complete the following tasks to ensure that data is forwarded to the expected portal:
  • On the portal that the data collector is moving from, assign the data collector to the No Data Collection configuration or move the data collector to a team that is assigned to No Data Collection.
  • Ensure that the data collector is active on the second portal.

If Robot Runtime continues to send data to the first portal or if the log message in the RuntimeLog.txt file shows that the working URL is still the first portal, check the contents of the No Data Collection client configuration (DesktopAnalyticsConfig.xml file). The DesktopAnalyticsConfig.xml file should contain only the <manifest></manifest> tags. If the file contains any content besides these tags, open a support incident using My Support Portal

What if a data collector is active on two portals at the same time?

Robot Runtime starts with the first URL listed for the urlOptions attribute and checks each URL in order. Robot Runtime sends data to the first URL where the data collector is currently active. 

What if the urlOptions attribute is missing or empty?

Robot Runtime sends data to the portal defined in the baseURL attribute. If your organization uses only one portal, enter the URL for your single portal using the baseURL attribute. You do not need the urlOptions attribute if you use a single URL. 

What if a URL in the urlOptions attribute is invalid?

Robot Runtime first checks the remaining URLs for the urlOptions attribute. Robot Runtime then uses the first valid URL where the data collector is active.

If the data collector is not active on any of the URLs in the urlOptions attribute, then Robot Runtime does not send data to any URL.

What if all of the URLs in the urlOptions attribute are invalid?

Robot Runtime does not send data to any Workforce Intelligence portal. 

Can I see which portal is receiving data for a data collector from the CommonConfig.xml file?

Robot Runtime does not rewrite the working URL back to the baseURL attribute in the CommonConfig.xml file. However, you can view URL details in the RuntimeLog.txt file. Look for the following entry in the RuntimeLog.txt file to see which portal is receiving data: 

| Using the working URL : -

Which URL details are in the RuntimeLog.txt file?

The following examples show the types of messages related to the urlOptions attribute:

Log messages when Robot Runtime checks for a valid URL

| Checking for a valid Intelligence URL

| Available URL options : -,

| Checking for url number 1 : -

Log message when Robot Runtime finds a valid URL

| Using the working URL : -

Log messages when a URL is invalid

| URL number 1 : - is not working.

| Checking for url number 2 : -

Log messages when all of the URLs invalid

| Checking for url number 2 : -

| URL number 2 : - is not working.

| No working intelligence URL found among the provided URL options

  • Previous topic What happens when you move a user to another team
  • Next topic Protection of Personally Identifiable Information in Workforce Intelligence

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us