INC-148154 · Issue 602921
Hot Fix Manager updated to use installation order for schema import
Resolved in Pega Version 8.3.5
Schema changes were not being imported during the hot fix manager DL import process. Investigation showed this was due to hotfixes in the DL being iterated over from newest to oldest, causing older hotfixes to replace the value added to a map by the newer. To resolve this, the system has been updated to use hotfix install order, which considers selected and dependent hotfixes, rather than ordering newest to oldest. This ensures that newer table representations will override older rather than the other way around.
INC-140279 · Issue 597756
JMX logging added to upgrade diagnostics
Resolved in Pega Version 8.4.4
In order to improve diagnostic information, infoForced loggers have been added for debugging upgrade issues related to JMX calls to enable and disable rules creation.
INC-144555 · Issue 603071
Changelog cleanup added for de-optimized properties
Resolved in Pega Version 8.4.4
Unwanted optimization was automatically added to properties for the Application-Work-Casetype class created using the wizard in the App Studio. Attempts to remove the optimization did not work: the property advance tab was showing the optimized classes details even after deleting and recreating the property. When a property is optimized the system adds entries to pr_changelog for the list of classes it has optimized. When the property was deleted, the pr_changelog was not cleared. This was a missed usecase, and has been resolved by overriding the Cleanup activity at Rule-Obj-Property class to delete the pr_changelog entry associated with that if it is present.
INC-144869 · Issue 606617
Improved ScalarPropertiesWriter logging
Resolved in Pega Version 8.4.4
In order to improve diagnostics, debug loggers have been added to ScalarPropertiesWriter.java to print column name in the logs while creating map between column names and their values from clipboard page.
INC-146595 · Issue 604791
Initialized entryName for light weight inventory instance
Resolved in Pega Version 8.4.4
When running deployment on a new pipeline created for the next minor version, once the deployment process got to the point of showing aged updates, the “view aged updates” came back as blank screen. Viewing the logs showed the aged update elements come back but were missing the pyName associated with them. Investigation showed that the system did not have support for setting the mEntryName for LightweightInventoryInstance objects. This has been resolved by adding a junit to ensure that getEntryName() doesn't return as null and should be equal to pzInsKey.
INC-148154 · Issue 602922
Hot Fix Manager updated to use installation order for schema import
Resolved in Pega Version 8.4.4
Schema changes were not being imported during the hot fix manager DL import process. Investigation showed this was due to hotfixes in the DL being iterated over from newest to oldest, causing older hotfixes to replace the value added to a map by the newer. To resolve this, the system has been updated to use hotfix install order, which considers selected and dependent hotfixes, rather than ordering newest to oldest. This ensures that newer table representations will override older rather than the other way around.
SR-B65434 · Issue 334578
Oracle table metadata performance improvements
Resolved in Pega Version 7.4
Performance improvements have been added for Oracle table metadata queries.
SR-B74189 · Issue 334576
Oracle table metadata performance improvements
Resolved in Pega Version 7.4
Performance improvements have been added for Oracle table metadata queries.
SR-B76468 · Issue 336009
Oracle table metadata performance improvements
Resolved in Pega Version 7.4
Performance improvements have been added for Oracle table metadata queries.
SR-B76989 · Issue 327639
Informational text added to "No suitable driver" error message
Resolved in Pega Version 7.4
After configuring Pega to connect to an external database using Data-Admin-DB-Name with a JDBC URL configuration that had the appropriate jar for the driver in the application server classpath, unexpected behaviors were seen. The first time the Test Connectivity button was clicked, a "No suitable driver found" error appeared. The second click ran the test as expected. This confusion was related to an undocumented enhancement: because adding a new database JDBC driver in Pega may require configuration to get the driver class loaded to the classpath, the 'No suitable driver' exception was enhanced with the configuration required to get the JDBC driver loaded at the next restart. In order to avoid confusion, informational text will now appear as part of the "No suitable driver" error message to explain this.