INC-160275 · Issue 628103
Unchecked Include descendant classes in pyFeedUserDetails report definition
Resolved in Pega Version 8.6
After upgrade from Pega 7.4. to Pega 8.4, the use of a custom class 'XX-Data-OperatorLoginDetails' which pattern-inherits from Data-Admin-Operator-ID was causing the error "Union not applied because properties [pyImageFileName, pyEmailAddress, pyUseLocale, pyDefaultTimeZone] are not optimized in Data-OperatorLoginDetails”. This happened when the case manager portal was launched and the report definition pyFeedUserDetails (introduced in newer releases) was running by default, and was due to the presence of a few unoptimized properties when the report definition had "Report on Descendant classes" - include all descendant classes, checked by default. To resolve this, the checkbox to Include descendant classes in pyFeedUserDetails is now set as unchecked by default.
INC-160295 · Issue 635008
Null check added for pzinskey in CSLoadSelectedArticle
Resolved in Pega Version 8.6
In step 5 of CSLoadSelectedArticle, there is a call to pzGetAssociatedTags. Step 1 of pzGetAssociatedTags is an Obj-Browse with MaxRecords set to 100000000, and there is logic to retrieve records where pxLinkedRefFrom = Primary.pzInsKey. If Primary.pzInsKey is null, then the Obj-Browse will fetch all of the records. In order to prevent an unnecessary flood of results, a when condition has been added in the CSLoadSelectedArticle rule to check pzInskey so that when the context is empty the system will not call the pzGetAssociatedTags and return the entire record set.
INC-160851 · Issue 631620
Multiple Pulse attachments deleted correctly from datapage
Resolved in Pega Version 8.6
If a Pulse post had only one attachment, removing the post using the Delete option correctly deleted the attachment from Link-attachment and Data-WorkAttach-File. However, if more than one attachment was present, the attachments were removed from view in the UI but were not deleted as expected from the datapage D_AttachmentList. This caused the pr_data_file table to grow very large. Investigation traced the issue to a 'when' condition in the PegaSocial-Message-ValidateDelete activity that was incorrectly being set to true due to a null value and causing the system to skip the deletefile step. This has been resolved by updating the logic to correctly handle removing multiple attachments on delete of a post.
INC-133214 · Issue 590380
Deployment Manager rollback works for directed inheritance
Resolved in Pega Version 8.6
Rollback was not working correctly in Deployment Manager for history classes using directed inheritance. This was traced to a redundant check in AbstractHistoryPageKeeper that enforced the history pages pattern inherited from one of the base history classes, and this has now been removed.
INC-140040 · Issue 597666
Improved handling to ensure circumstanced rules skim is complete
Resolved in Pega Version 8.6
After performing a major rule skim, it was noticed that some of the circumstanced rules were not carried over to the higher version. The data was restored and a second skim was attempted. Once again, not all of the circumstanced rules were carried over; however, the results were different than in skim 1. This issue was traced to the circumstanced rule and base rule having the same pxCreateDateTime because they were processed with in a millisecond span. To resolve this, a 1ms explicit sleep has been added before processing each record.
INC-140279 · Issue 597757
JMX logging added to upgrade diagnostics
Resolved in Pega Version 8.6
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-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.