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-B38619 · Issue 298574

Action item refresh properly triggers

Resolved in Pega Version 7.3

Refresh was not clearing the temporary filters applied on the report definition results if the refresh option was triggered by the actions button. This has been fixed by adding a new java step to pzRunWrapper activity to clear the previously applied filters.

SR-B38674 · Issue 301022

Descendant class logic made more robust

Resolved in Pega Version 7.3

The 'Report on descendant' option in the report definition/Listview was giving incorrect results. This was caused by the code used to execute the RD looking up the descendant class from the current application that inherits from the applies-to class (tools.getDatabase().getConcreteDescendantsInCurrentApplication(class name);) of the RD and executing the RD against this class. While this is appropriate when an application is built on another and case types are directly inherited into the new layer, this will not work when application layers are added which do not include equivalent case types for every case from the built upon applications. This becomes a more common problem when the MBO feature starts getting used more often on the customer implementations. To ensure the descendant class is correct, the Useimplemenation class has been updated to be more robust.

SR-B38958 · Issue 296022

Updates to field values reflected on mobile

Resolved in Pega Version 7.3

After updating field values in higher ruleset versions and forcing a full data sync, the mobile app did not reflect the updated value. This was due to rule resolution not happening while packaging the FieldValue rules due to locale, and has been corrected by changing the PZGETFIELDVALUES rule to sort the pzInsName based on the ruleset versions and picking the latest available rules from the ruleset.

SR-B38980 · Issue 299227

createDateTimeCategories function modified to use operator time zone

Resolved in Pega Version 7.3

A report definition chart using the operator time zone of "Europe/London" and locale "en_US" displayed duplicate date columns. Updating the operator time zone to "America/New_York" removed the problem. This issue was caused by the system always parsing/formatting the date with the default local time zone, and has been resolved by modifying the parseDate/formatDate/createDateTimeCategories function to use the operator time zone instead.

SR-B39293 · Issue 296727

Mobile checkbox controls fire validations

Resolved in Pega Version 7.3

Validations were not fired on checkbox controls on a mobile application; the same scenario worked fine when tested on the desktop. This was due to a missing Validation Attributes property, and has been fixed.

SR-B39293 · Issue 297091

Mobile checkbox controls fire validations

Resolved in Pega Version 7.3

Validations were not fired on checkbox controls on a mobile application; the same scenario worked fine when tested on the desktop. This was due to a missing Validation Attributes property, and has been fixed.

SR-B39293 · Issue 299867

Mobile checkbox controls fire validations

Resolved in Pega Version 7.3

Validations were not fired on checkbox controls on a mobile application; the same scenario worked fine when tested on the desktop. This was due to a missing Validation Attributes property, and has been fixed.

SR-B39484 · Issue 296141

Calculation Builder made more robust for use in segments

Resolved in Pega Version 7.3

An error was generated when using the Calculation Builder in a segment, though the Calculation Builder for Report Definition worked. This was traced to code in the Calculation Builder which assumed the report page class would always be "Rule-Obj-Report-Definition", which failed for segments. To correct this, the logic has been modified to be more robust.

SR-B40310 · Issue 299601

Offline sync fixed for post-processing Question shape

Resolved in Pega Version 7.3

The post-processing activity of a Question shape was not skipped when 'only execute post processing on client' was checked on the case type rule. A 'when' condition has been added for the post processing activity of Question Flow to fix this.

SR-B40812 · Issue 304049

New section made available for customized RB report generation date

Resolved in Pega Version 7.3

In order to support customized formats in the generated date used by Report Browser, the new section PYDISPLAYREPORTGENERATEDDATETIME has been made available. This is accessed through pzDisplayReportSectionForPDF, and replaces the "generated on" datetime property used previously.

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