Handling class mapping limitations

Handling class mapping limitations

Description	Describes how to modify class mappings to adhere to the 30-character limit after upgrading to Robot Manager 8.5 in an Oracle environment 8.5 Robotic Process Automation.
Version as of	8.5
Application	Pega Robotic Process Automation
Capability/Industry Area	Robot Manager

This content is being retired in the next few months. Please use our documentation site https://docs.pega.com to find information you may need.

Handling class mapping limitations

Earlier versions of the Oracle database limited table names to 30 characters or less. Pega software creates table name that meet this restriction. However, the update has a known issue that prevents a class mapping from being created with the correct length. This prevents some Robot Manager functionality from working correctly. For example, this problem can prevent you from using the Robot Manager Dashboard to assign the RuntimeConfig.xml file to a Robot Runtime user.

To avoid problems, manually update the class name mapping to match the trimmed name.

Note: This only happens when you upgrade from Oracle 12c or earlier to Oracle 19c. The table names change from 32-bit to 64-bit.

Modify class mappings

To update a class name table mapping, perform the following steps in Dev Studio:

1. Click Records -> SysAdmin -> Database Table.
2. Find and open the classname record that you need to modify.
3. Update the table name with the shortened name.
4. Save the record.
5. Update the following class names to match their shortened name:

ClassName

Data-Robot-AssignmentType-Metadata

Data-Robotic-NotificationAlert

Data-Robotic-OperationalStatistics-Exception

Data-Robotic-OperationalStatistics-Exception-Archive

Data-Robotic-OperationalStatistics-Health-Archive

Data-Robotic-OperationalStatistics-Usage-Daily

Data-Robotic-OperationalStatistics-Usage-Daily-Archive

Data-Robotic-OperationalStatistics-Usage-Hourly

Data-Robotic-OperationalStatistics-Usage-Hourly-Archive

Data-Robotic-OperationalStatistics-Usage-Monthly

Data-Robotic-OperationalStatistics-Usage-Monthly-Archive

Data-Robotic-OperationalStatistics-Usage-Yearly

Data-Robotic-OperationalStatistics-Usage-Yearly-Archive

Data-Robot-Metrics-ActivityStatus-Archive

Data-Robot-Metrics-UnderPerformingBots

Data-Robot-Metrics-UnderPerformingBots-Archive

History-Data-Robot-Automations-Archive

History-Data-Robot-Events-Archive

History-Data-Robotic-Config-Runtime

History-Link-Robotic-RuntimeConfigAssignment

Link-Robotic-RuntimeConfigAssignment

Finding the trimmed table names

To find the trimmed table name for the class name, choose Configure > System > Database > Schema Change Tracking.

An action that does not require human involvement but can instead be done programmatically.

A business solution that automates workflows in your organization. Multiple, unrelated applications can be hosted in the same system. You create an application by running the New Application wizard.

One of the following UI elements:

- A centralized workspace that displays operational information about your application and key performance indicators, such as the number of assigned items or the average time to resolve a case. A dashboard can include charts, reports, worklists, and other widgets.

- A single webpage that shows the current status and ongoing trends of your organization’s behavior. This data helps you to make informed decisions and guides you to specific investigations or outcomes.

Contains the configuration settings that are primarily used by Pega Robot Runtime. Pega Robot Runtime is installed as a stand-alone application and is also installed with a Pega Robot Studio installation.

A named Pega Robot Runtime user whose desktop usage is being actively captured.

A collective term that describes a rule instance or a data instance. For example, a customer record would include data specific to a given customer, such as name, telephone number, and customer account number.