SR-B73478 · Issue 325315
Chart date column duplication resolved
Resolved in Pega Version 7.3.1
Report definition charts were displaying duplicate date columns when the operator time zone was set to "Europe/London". To correct this, the system will conditionally set the time zone only when it's a datetime when normalizing the data.
SR-B73531 · Issue 325518
Missing check added for "Column Command Menu" on summary type report
Resolved in Pega Version 7.3.1
For a summary type report, the column command menu was still displayed even though the "Enable Column Command Menu" was unchecked on the report definition Report Viewer tab. This was due to a missing check for "Enable column command menu" before adding the showReportRCMenu onclick event, and has been fixed.
SR-B74586 · Issue 325692
Fixed save-as for RD with sub-report and join
Resolved in Pega Version 7.3.1
A save-as for the existing Report Definition rule :USCANSaleEstimate was not working for a new ruleset version. This was an issue with an existing RD that had a sub-report and was joined by a column in the sub-report that was a function, and pzGenerateMsgForUderDefinedFunctions has been modified to correct this.
SR-B76880 · Issue 326010
Repeat grid filtering option fixed for Microsoft Internet Explorer 11
Resolved in Pega Version 7.3.1
The repeat grid populated when running report definition was prompting for the filter of the data properly in Microsoft Internet Explorer 11, but no action was performed when clicking on it. This was an issue with missing navigation rule changes, which have been added.
SR-D39956 · Issue 511637
Corrected method IF use with shortcut function
Resolved in Pega Version 8.2.5
After upgrade, method IF was not working as expected when used in an expression like "@if(.totalorders_120days>0,(.remakeorders_120days/.totalorders_120days)<0.3,false)". This was caused by a missed use case for the combination of an exception-generating function in combination with a shortcut function (i.e. ternary, and, or), and has been resolved.
SR-D41207 · Issue 512087
Fallover stategy added to chat routing to keep event processor running
Resolved in Pega Version 8.2.5
Chats were becoming stuck in the queue and end users were not able to connect with the customer service representative. An excessive number of queued items were observed in a Queue Processor named "EventProcessor". This was traced to the setting "Browse from the offset" having been removed because of a retention policy. This resulted in "Browse from the end of the stream" being used instead even though browse should start from the earliest known offset. To resolve this, Stream Producer will be cached based on topic, and Stream consumer will fall over to an earliest strategy in case the requested offset isn't found so the event queue will be handled in a timely manner.
SR-D42662 · Issue 516870
Support added for auto restart of system paused nodes
Resolved in Pega Version 8.2.5
After the system paused a run, nodes had to be manually restarted by hand. Investigation showed that a node had fallen from the Hazelcast cluster due to an instability and that there was no support for an auto-restart under this condition. This has been resolved by adding a pulse task to resume runs stuck in system pause.
SR-D43912 · Issue 509737
Fallover stategy added to chat routing to keep event processor running
Resolved in Pega Version 8.2.5
Chats were becoming stuck in the queue and end users were not able to connect with the customer service representative. An excessive number of queued items were observed in a Queue Processor named "EventProcessor". This was traced to the setting "Browse from the offset" having been removed because of a retention policy. This resulted in "Browse from the end of the stream" being used instead even though browse should start from the earliest known offset. To resolve this, Stream Producer will be cached based on topic, and Stream consumer will fall over to an earliest strategy in case the requested offset isn't found so the event queue will be handled in a timely manner.
SR-D47618 · Issue 512602
Statistic rounding error in ADMSnapshot Agent with Oracle corrected
Resolved in Pega Version 8.2.5
While running the ADMSnapshot Agent, the exception "internal.mgmt.Executable) ERROR com.pega.decision.adm.client.ADMException: Failed to complete ADM Data Mart snapshot" was seen. This was traced to an issue with the rounding of performance statistics when using Oracle, and has been resolved.
SR-D47713 · Issue 511970
Corrected issue with strategy framework testing
Resolved in Pega Version 8.2.5
Issues were seen in creating a dataflow to test the strategy framework shipped with the Pega Marketing product. It was not possible to use a data transform to test this strategy because it is in the shipped PegaMKTEngine ruleset. Investigation showed the value of appliedToClass was retrieved from "pyRunOnDataFlowClassName" instead of from the running strategy, and this has been resolved.