INC-118907 · Issue 561071
ClearHighlight called after test steps complete
Resolved in Pega Version 8.2.7
When using a custom delay as part of a scenario test, an orange highlight square was unexpectedly persisting on the portal. To resolve this, an update has been made to explicitly call "_clearHightlight()" after every test case step execution completes.
INC-194269 · Issue 681046
Added handling for Create Source and Target properties of Date
Resolved in Pega Version 8.7
A report definition was not displaying results after update, and a stack overflow was reported. This was a missed use case for Create Source and Target properties of Date, and has been resolved by adding a boolean flag to avoid autochain during validations when data type is Date.
INC-186138 · Issue 668811
Charts sourced from Report Definition show correct color post-update
Resolved in Pega Version 8.7
After update, the color coding was not working on charts sourced from a report definition. This was due to the correct seriesType not being determined when function aliases were used in charts, and has been resolved by adding a condition in configuration.java to determine correct the SeriesType.
INC-199341 · Issue 694713
Content-type values made consistent
Resolved in Pega Version 8.5.6
The content-type for service APIs was returned as 'text' for 401 errors when using a custom authentication type instead of the parent-type/child-type format such as text/plain, text/html, application/json, etc. This has been corrected.
INC-186138 · Issue 668809
Charts sourced from Report Definition show correct color post-update
Resolved in Pega Version 8.5.6
After update, the color coding was not working on charts sourced from a report definition. This was due to the correct seriesType not being determined when function aliases were used in charts, and has been resolved by adding a condition in configuration.java to determine correct the SeriesType.
INC-172546 · Issue 652880
Resolved classcast exception with assembled HTML controls
Resolved in Pega Version 8.7
A classcast exception was being generated on login. Investigation showed the Static Assembler was unexpectedly using a different Assembler to assemble the Html control rule. Standard behavior is that StreamBuilderAssembler assembles controls of type StreamBuilder and ControlAssemblerForVTable assembles controls of type ControlBuilder. In this case, static assembly for HTML controls using VTable was performed using StreamBuilderAssembler, causing a classcast exception when using VTable because the instance of the generated.html class was incorrectly inheriting from StreamBuilder (the parent class of ControlBuilder) instead of ControlBuilder which is the specified interface in the generated.html Java code. This has been resolved by updating the system to skip rules of type 'Rule-HTML-Property'(control) during Static Assembly.
SR-D88500 · Issue 562655
Eligibility prompt integer values sorted by incremental size
Resolved in Pega Version 8.2.7
In an Offer rule on the Eligibility tab of the Eligibility Builder, an eligibility row using {integer property} comparator {value} had the list of prompt values sorted alphabetically for integer values rather than incremental size when using Select value -> Existing Values. This has been corrected by revising the logic in addValuesToOutputPage to call Report.sort with different sorting algorithm for numeric values. Logic was also updated to call Report.sort for prompt lists.
INC-186889 · Issue 674014
Unused DSS compiledExpressions now defaults to false
Resolved in Pega Version 8.7
After updating from Pega 8.2 to Pega 8.5, executing a test campaign failed with an error in logs. This occurred when running Distribution tests with "Include funnel analysis reports" checked, and was traced to the DSS setting "decision/strategy/ssaVM/compiledExpressions". As this was previously used to toggle a feature which is no longer in use, the default setting for this DSS has now been changed to false to resolve this issue.
INC-198232 · Issue 685700
Tombstone cleanup modified to handle very large volume environments
Resolved in Pega Version 8.7
Cassandra nodes were periodically suffering from an out of memory condition. This was traced to tumbling windows creating too many tombstones for Cassandra to clean up effectively when running in a very high volume environment with a short tumbling time. This has been resolved by modifying the procedure away from using individual tombstones to instead use range tombstones which will continuously supersede the previous tombstone so there is never an opportunity for them to build up.
INC-192833 · Issue 678115
New Application Wizard will default to existing work groups if none are created
Resolved in Pega Version 8.7
When using the new application wizard to create a new application, the new app API replaces the old work pools with the newly generated ones. If the new application configuration was done in such a way that classes are not generated due to reusing existing classes, access groups were being generated with empty work pools. To resolve this, the system has been updated to use the existing work pools if the new app didn't generate new work pools.