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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-118213 · Issue 184519

Refresh When' behavior fixed for portal tabs

Resolved in Pega Version 7.1.8

When a 'Refresh When' was active on a portal tab, the system would become unresponsive while trying to refresh it. This was caused by an incorrect element call resulting in a JavaScript error and has been corrected.

SR-118224 · Issue 182305

Report Definition "Pick Value" list resolves to correct layer

Resolved in Pega Version 7.1.8

When a report definition in the framework layer has "Report on descendant class instances" checked, running the report from the implementation layer should retrieve pick list values for "Available Values" on filter popup from the implementation layer. Instead, it was getting the values from the framework layer. This was caused by the code that generates the SQL query to populate the "Pick Value" list resolving to the wrong work class name, using the framework layer work class rather than the implementation layer work class. There was a workaround of performing a 'Save As' of the affected reports to each implementation layer, but this has been fixed.

SR-118224 · Issue 182203

Report Definition "Pick Value" list resolves to correct layer

Resolved in Pega Version 7.1.8

When a report definition in the framework layer has "Report on descendant class instances" checked, running the report from the implementation layer should retrieve pick list values for "Available Values" on filter popup from the implementation layer. Instead, it was getting the values from the framework layer. This was caused by the code that generates the SQL query to populate the "Pick Value" list resolving to the wrong work class name, using the framework layer work class rather than the implementation layer work class. There was a workaround of performing a 'Save As' of the affected reports to each implementation layer, but this has been fixed.

SR-118269 · Issue 174402

Eform wizard upload error resolved

Resolved in Pega Version 7.1.8

When attempting to upload a file using the EForm wizard, an error was generated stating "The Flow Action post-processing activity PopulateFileRule failed" and the file did not upload. The root cause of this ruleset problem was that the necessary class was not present in the JAR, and has been resolved.

SR-118283 · Issue 180166

Create New Work functionality smoothed for flows across multiple windows

Resolved in Pega Version 7.1.8

The Create New Work functionality in IAC was intermittently rendering incorrect data when opening a workflow in multiple windows. This was found to be a problem with PostDataId generated duplicate IDs for the different requests and has been changed to generate unique IDs.

SR-118440 · Issue 178175

Sorting fixed for RD Repeat Grids with joined properties

Resolved in Pega Version 7.1.8

When sorting a Repeat Grid based on a Report Definition, if the user tries to sort on a property from a join then it would fail with the error 'Cannot get property information for: Assign-Worklist..' This was caused by ObjClass being missing for few elements of page list, and has been fixed. In addition, a check has been added to ensure proper handling in cases where Obj class is missing.

SR-118474 · Issue 182925

Corrected time zone mismatch in Report Browser

Resolved in Pega Version 7.1.8

If a server and an operator had different time zones set, reports that were scheduled through the report browser to run and deliver notifications to a list of recipients would run immediately if the schedule was modified. To handle this time zone difference, "Pega-ScheduledTask.pzPostProcess" has been modified to use the time zone from calendar in the formatter.

SR-118474 · Issue 178295

Corrected time zone mismatch in Report Browser

Resolved in Pega Version 7.1.8

If a server and an operator had different time zones set, reports that were scheduled through the report browser to run and deliver notifications to a list of recipients would run immediately if the schedule was modified. To handle this time zone difference, "Pega-ScheduledTask.pzPostProcess" has been modified to use the time zone from calendar in the formatter.

SR-118486 · Issue 175139

XSS filtering improved for Host and Gateway

Resolved in Pega Version 7.1.8

For security, XSS filtering has been improved on hostconfig.jsp and GatewayAdminUtils.java .

SR-118602 · Issue 178489

Corrected flow action dropdown execution

Resolved in Pega Version 7.1.8

For certain work objects, selecting a flow action from the pyAction area resulted in an error message and the flow action did not execute. A sample error message might be "The FlowAction ... could not be added to this assignment." This was caused by a flaw in the code which assumed that simple integer IDs in the DOM are unique. The code that handles 'Take Action' input has been re-factored to be more robust.

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