Handling class mapping limitations

From PegaWiki
Modifying class mappings after upgrading to Robot Manager 8.5 in an Oracle environment / This is the approved revision of this page, as well as being the most recent.
Jump to navigation Jump to search

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 Robotic Process Automation
Capability/Industry Area Robot Manager



Handling class mapping limitations[edit]

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 upgrade 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[edit]

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[edit]

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