Skip to main content


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

Setting up Pega Platform to use reports in Pega Robot Manager

Updated on December 20, 2022

During the installation of Pega Robot Manager, the required Robot Manager configurations are turned on by default. As a system administrator, review the settings to ensure that your application is optimized for Elasticsearch reporting.

Pega Robot Runtime 19.1.64 or later is required for reporting.
  1. Log in to Dev Studio as a system administrator.
  2. Verify that at least one of the active nodes has a node type which contains Search or is set to Universal.
    For more information about nodes, see Assigning node types to nodes for on-premises environments.
  3. In the navigation panel of Dev Studio, click RecordsSysAdminDynamic System Settings, and confirm the values of the following Data Admin System settings:
    • indexing/useDataInstances row (owning ruleset: Pega-SearchEngine) – true.
    • reporting/searchdata/enabled (owning ruleset: Pega-Reporting) – true.
    • pegarobotics/defaultTimezoneForRMReporting (owning ruleset: Pega-Robotic-AutomationPackageManagement) – GMT.
      Note:
      • The defaultTimezoneForRMReporting setting provides the preferred timezone for the Collection Interval column of daily, monthly, and yearly usage reports. Hourly reports use the time zone defined on the requestor's Operator ID record.
      • Do not modify this setting to avoid discrepancies between, on the one hand, hourly reports and, on the other hand, the matching daily, monthly, or yearly reports.
  4. In the navigation panel of Dev Studio, click RecordsSysAdminQueue Processor, and confirm the values of the following queue processors:
    • pyBatchIndexClassesProcessor – the Enable Queue Processor switch is turned on.
    • pyBatchIndexProcessor – the Enable Queue Processor switch is turned on.
  5. In the Instances of Queue Processors list, select the pyProcessOperationalStatistics queue processor.
    1. Confirm that Dev Studio displays the following message at the top of the screen: All queue processors are rule resolved against the context specified in the System Runtime Context:
    ChoicesActions
    Dev Studio displays the messageGo to step 6.
    Dev Studio does NOT display the message
    1. Click System Runtime Cotext.
    2. In the Applications section, click Add application.
    3. In the Name field, enter PegaRobotManager.
    4. In the Version field, enter 8.
    5. Click Save.
    6. Wait for the system to refresh.
  6. Configure the Associated with node type and Number of threads per node fields according to the expected load.
  7. At the top of the screen, on the toolbar, click ConfigureSystemSettingsSearch.
  8. Click Dedicated.
  9. Under the Status column, ensure that the status of all dedicated indexes for Usage statistics is AVAILABLE.
What to do next: Configure your robotic workforce to send operational data for use in reporting.
    • Previous topic Configuring reporting in Pega Robot Manager
    • Next topic Enabling the collection of Pega Robot Runtime data for reporting

    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.

    Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us