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.

INC-119669 · Issue 562588

Special character handling added to filters for table sourced with parameterized RD

Resolved in Pega Version 8.1.9

Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.

INC-145810 · Issue 599463

BIX log shows correct corrupted BLOB pzInskey

Resolved in Pega Version 8.1.9

An update has ben made to ensure the correct inskey is shown in the BIX logs for a corrupted BLOB.

SR-D90400 · Issue 563187

Explicit parent added for descendants in subreport to correct summary

Resolved in Pega Version 8.1.9

When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.

SR-A76252 · Issue 253236

String filter values treated consistently

Resolved in Pega Version 7.2.2

Attempting to schedule a report with a string value in the filter condition caused a parsing error even when the report ran correctly in DesignerStudio. To resolve this and make the behavior consistent, the logic has been updated such that If filter value is string but not a property reference, then do not resolve it.

SR-A85953 · Issue 254446

Fixed Export to Excel

Resolved in Pega Version 7.2.2

Export to Excel from report definition generated the sporadic error "Unable to read file." This was traced to the browser attempting to open the file before it was downloaded, and code has been added to check the browser and handle the download/open appropriately.

SR-A76558 · Issue 253570

Date/time data fixed for sub-report filter

Resolved in Pega Version 7.2.2

It was not possible to select filter value for the sub report date column value in main report filter condition due to the sub report date time column value not being populated correctly. This has been fixed.

SR-A24877 · Issue 250548

Widget title localization corrected

Resolved in Pega Version 7.2.2

Sporadic issues were seen with proper localization for the label of items inside any widget of the widget library. A step has been added to explicitly set the pyDescription fix this.

SR-A76162 · Issue 251024

Widget title localization corrected

Resolved in Pega Version 7.2.2

Sporadic issues were seen with proper localization for the label of items inside any widget of the widget library. A step has been added to explicitly set the pyDescription fix this.

SR-A67716 · Issue 251384

Updated ruleset determination for saving copied reports

Resolved in Pega Version 7.2.2

When a new report was made from a copy, it was not properly assigned to the ruleset it should be saved in (the "design time" ruleset configured on the operators Access Group). Instead, it was residing in the same ruleset as the template report definitions (Pega-Reporting), causing property validations to fail if they were in the subset of rulesets which were in the design time ruleset's stack but not in Pega-Reporting until the report was saved successfully once. This has been fixed by adding a step to Rule-Obj-Report-Definition!pxShowReport that sets the ruleset name and version of a new report to match the Access Group's configured design time ruleset.

SR-A21741 · Issue 250251

Filtering and drill down fixed for encrypted values

Resolved in Pega Version 7.2.2

When one of the fields on a drill down report was encrypted, filtering would show the encrypted value but the drill down would not. This was an issue with the encoding attached to the encrypted element not being handled consistently, and has now been fixed.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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