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-128206 · Issue 192572

Added null check for RD column containing a function

Resolved in Pega Version 7.1.8

When running a report definition with a column that has a function, it showed the error "illegal zero-length identifier". This was due to the alias name for the Rule-Alias-Function with return type 'True or False' being empty in the pxSQLStatementPost function, and a check has been added to handle this.

SR-128320 · Issue 193581

Updated chart export handling for Safari

Resolved in Pega Version 7.1.8

The charts in reports are getting disappeared on click of When using the Safari browser, clicking on Export to Excel/Export to PDF caused the charts in reports to disappear. This was traced to the form target being blanked in the browser handling, and a browser check has been added to invoke special handling for Safari..

SR-128689 · Issue 194302

Enabled line wrap for Display Shortcuts in RD

Resolved in Pega Version 7.1.8

Report definition was cutting off a long description rather than wrapping it to a new line. This was traced to pzDisplayShortcuts (a final rule) not being set to wrap text, and that setting has now been enabled.

SR-128701 · Issue 194839

getPropertyValue name collision resolved

Resolved in Pega Version 7.1.8

In order to accommodate custom RUFs called 'getPropertyValue', the Pega version of the rule is now called with full Library qualification.

SR-128883 · Issue 195834

Fixed button contrast when using accessibility

Resolved in Pega Version 7.1.8

The "Select Values" button in the dialog to edit report filter had a low contrast ratio when accessibility was enabled. This was caused by the unintentional application of the repeat layout CSS to the button, and has been fixed.

SR-129171 · Issue 195047

Corrected error in order of operations for Numeral builder

Resolved in Pega Version 7.1.8

The Add function in reporting was not returning the proper result when included in an equation with multiple order of operations. This was an error in the Numeral function builder, and has been corrected.

SR-129592 · Issue 196979

Scheduled report now checks default max records value

Resolved in Pega Version 7.1.8

When scheduling a report definition, the default value for max records to export was ignored when run by a scheduled task agent but used if the report was run manually. This value is normally set to 10,000 in the system settings and should be the default unless an override value has been entered for "Maximum Number Of Rows For Export" on the Data Access tab. To correct this issue, the pzRunScheduledShortcut activity has been updated to use the default if no value has been entered.

SR-129733 · Issue 199324

Enabled word wrap for RD export to PDF

Resolved in Pega Version 7.1.8

After export to PDF from RD, values were getting truncated or being displayed under the column and the column alignment was disrupted. Word wrap has been enabled to fix this display issue.

SR-128430 · Issue 194956

Pagination removed from OwnersList to facilitate large category lists

Resolved in Pega Version 7.1.8

After having created a large number of categories from the "Reporting" landing page, the list of available owners was not the expected one when creating a new shortcut. The owner drop down list is generated by the ListView called "Rule-Category.pzGetCategoryOwnersList." Unfortunately this ListView is a FINAL rule and paging was enabled with a default count of 50 entries. In order to allow for customizations like the above, OwnersList has been modified to disable paging.

SR-128696 · Issue 195043

Fixed alignment of columns and headers in RD scroll headers setting

Resolved in Pega Version 7.1.8

If "Do not scroll header" was checked in Report Definition, there was an alignment issue with the header and report Data. This has been fixed by updating "GenerateCellContent" to generate the CSS classes in the markup, and the CSS style was added to "pyReportEditorStyling" and is commented to make it available there if desired.

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