Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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.

SR-A18481 · Issue 238244

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-A18493 · Issue 235336

Cross-browser checks added for disabled checkboxes

Resolved in Pega Version 7.2.1

The Checkbox Caption was not properly not disabled on Microsoft Internet Explorer when the checkbox was disabled due to a missing definition for the parent element. Extra condition have been added to find the disabled value of radiobutton and checkboxes regardless of browser.

SR-A18550 · Issue 234678

Strategy and data flow behavior more consistent

Resolved in Pega Version 7.2.1

Strategy execution via data flow was producing different results depending on how it was executed. This was caused by the use of different types of pages based on the execution method, and the code has been updated to produce more consistent behavior.

SR-A18624 · Issue 239177

Fixed post-upgrade data table conversion to local storage

Resolved in Pega Version 7.2.1

After upgrade, updating a data table into a local storage source generated the error "Cannot change keys for a class with (725) instance(s) ". This occurred when the local variable ?classKeysChanged? is true, which happened during comparison of the Key fields of the step page (classPage) and the primary page (ClassForm) because the order of the keys had changed even though the number of keys were same. The "AddProperties" activity has now been modified to check if there are keys already set in the class and if there are any, then skip resaving the class and exit the activity.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us