SR-A18100 · Issue 234215
BIX documentation updated for new "-J" timezone conversion option
Resolved in Pega Version 7.2.1
A -J option has been added to BIX to allow the specifying the timezone for datetime properties to be converted to when written to the XML output file. The documentation is as follows: A new command line option J is being added to take in a user specified time zone for e.g., UTC+05:00 format(s); If the specified timezone is not valid, it defaults to GMT example :How to specify this option: "-J" "UTC+5:30"
SR-A18193 · Issue 238469
SystemCleaner correctly purges pr_perf_stats
Resolved in Pega Version 7.2.1
It was noticed that SystemCleaner was working well except for a periodic dramatic purge that suddenly filled logs and sometimes caused a system crash. When BIX runs via command line, this updates the associated DSS in the application. If the DSS usage/usagetrackingenabled or its associated prconfig.xml setting are set to false, Step 12 of the SystemCleaner does not perform a number of activities including regular purging the pr_perf_stats table. This has been modified to remove the setting usage/usagetrackingenabled from prconfig.xml as agents are by default enabled.
SR-A18230 · Issue 234568
Enabled SLA calculations for drag and drop reassignments
Resolved in Pega Version 7.2.1
SLA was not firing when an assignment was dragged and dropped from a workbasket to a work list and vice versa. This was due to a missing update to the assignment handle for the queue item, and has been fixed.
SR-A18236 · Issue 236897
Workbasket re-visit issue resolved
Resolved in Pega Version 7.2.1
After selecting a workbasket in the MyGroup drop down and launching the pop-up containing the workbasket details, an error in the closing reset function led to an issue where a second workbasket would need to be launched before it was possible to return to the first one again. This has been corrected.
SR-A18261 · Issue 235785
CaseManager Following list properly updating work
Resolved in Pega Version 7.2.1
When there was at least one participant (workparty), clicking on the follow link in the Case Manager would only give the current status and would not update unless the workparty was unfollowed and followed again. This was required each time to get the updates. The issue was with the declare indexes not being generated correctly because of missing metadata between the workpage and workparty while doing a page copy. This has been fixed.
SR-A18333 · Issue 237135
Corrected JSON page group handling
Resolved in Pega Version 7.2.1
If DataSet-Execute method was used to cache a CustomerPage from Clipboard, using the same DataSet-Execute method to retrieve it from the cache using the "Browse by key" operation was not working correctly: If the page contained a page group property, then the retrieved CustomerPage contained additional invalid entries that led to errors in the mapping logic. This was an issue with the Clipboard page JSON converter not properly handling page groups, and has been corrected.
SR-A18370 · Issue 236447
Report category names localized
Resolved in Pega Version 7.2.1
Localization has been added for the standard reports category to translate values for AssignmentMonitoring, PerformanceAnalysis, WorkMonitoring, WorkAnalysis, and Guardrail Reports.
SR-A18404 · Issue 235467
New parameter to disable logging of Tidy PDF processing warnings
Resolved in Pega Version 7.2.1
When purge/archive was enabled, the system logs were filling with Tidy warning errors during PDF conversion. To resolve this, the new parameter 'pyShowWarning' has been added to the HTMLTOPDF Activity: set it to 'false' to avoid Tidy processing warnings in logs.
SR-A18464 · Issue 234927
"Grand Total" localized
Resolved in Pega Version 7.2.1
Localization has been added for the pyFieldCaption property "Grand Total" .
SR-A18466 · Issue 235142
Updated getDate function to use UTC
Resolved in Pega Version 7.2.1
Setting the system to the Brazil time zone ("UTC-03:00 Brasilia") with the operator set to Brazil/Acre caused a duplicate day to appear in October of every calendar year when the Microsoft Internet Explorer browser was used. This was traced to a difference in how the getDate function performed on the browser, and that function has now been updated to use getUTCDate() instead of getDate() to ensure cross-browser consistency.