INC-142236 · Issue 595979
Apache Struts updated
Resolved in Pega Version 8.6
The Apache struts2-core.jar and its dependencies have been updated to version 2.5.25.
INC-144555 · Issue 603070
Changelog cleanup added for de-optimized properties
Resolved in Pega Version 8.6
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-144864 · Issue 599145
Unneeded AUC error percentage calculation removed for better system performance
Resolved in Pega Version 8.6
When generating snapshots of the ADM models, an inefficiency in the metric calculation for the AUC error percentage caused an excessive amount of memory to be allocated which could cause slowdown or require a system reboot. This has been resolved by removing the problematic AUC error percentage calculation as it is not used in the UI.
INC-144869 · Issue 606616
Improved ScalarPropertiesWriter logging
Resolved in Pega Version 8.6
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-146477 · Issue 602203
Apache Struts updated
Resolved in Pega Version 8.6
The Apache struts2-core.jar and its dependencies have been updated to version 2.5.25.
INC-146595 · Issue 604790
Initialized entryName for light weight inventory instance
Resolved in Pega Version 8.6
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 602920
Hot Fix Manager updated to use installation order for schema import
Resolved in Pega Version 8.6
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-151418 · Issue 610231
Authentication updated for legacy activities
Resolved in Pega Version 8.6
Authentication updates have been made for several legacy activities invoked via URL by custom HTML.
INC-153138 · Issue 625568
Database primary keys generated as NONCLUSTERED for imports
Resolved in Pega Version 8.6
When a primary key was defined for a table and the table was exported and then imported, the primary key was generated as CLUSTERED. This resulted in an MS SQL Cluster Index violation because all Pega-shipped tables generated during installs/upgrades have a PK constraint index with NONCLUSTERED index type as it allows for a longer key. This was a missed use case, and has been resolved by updating the system such that when importing with MS SQL database, the primary key index is made NONCLUSTERED all the time so it will be consistent with the base platform.
INC-153182 · Issue 615758
Corrected import overriding class definition history save setting
Resolved in Pega Version 8.6
Importing Robot Manager RAPs was failing due to a bad class mapping between class History-Data-Robotic-AutomationPackage-DeploymentLevel and its corresponding table pr_hist_datadeplvl in database PegaDATA. This was traced to a conflict where the class wasn't designed to have history saved but import was passing a flag that forced history to be saved which was overriding the class setting. This has been resolved.