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-B30410 · Issue 294913

Report drilldown works with 'do not display group headings'

Resolved in Pega Version 7.3

When sub-report properties were used in the main reports column source, the report definition displayed the expected results when clicking on a configured drilldown report and chart but displayed no results when listview dataset was clicked. This was traced to having "Do not display group headings" enabled in combination with drilldowns, and has been resolved.

SR-C90467 · Issue 429607

Validations are correctly run on rescheduled reports

Resolved in Pega Version 8.3

When using the out-of-the-box schedule report functionality, UI validations were bypassed if the existing schedule was deleted and the report was rescheduled. This has been corrected by updating the Review harness to display the Perform harness when clicking Update.

SR-C74054 · Issue 422024

Handling added for summary columns in Export to Excel

Resolved in Pega Version 8.3

When a field has an aggregate function in Report Definition, the column alias changes and is not the same as the property name. The consequence is a mismatch between the result set column name and the property name from the property list created beforehand. This results in blank fields when using the "pxDownloadDataRecordsAsCSV" activity for Export to Excel. In order to support the export of summarized columns in Report Definition, an enhancement has been added that uses the column label as an alias for aggregate fields in the native SQL builder of the exportData API to form a map between the property name and the alias name and use it while iterating over the result set.

SR-D18256 · Issue 490790

Handling added for summary columns in Export to Excel

Resolved in Pega Version 8.3

When a field has an aggregate function in Report Definition, the column alias changes and is not the same as the property name. The consequence is a mismatch between the result set column name and the property name from the property list created beforehand. This results in blank fields when using the "pxDownloadDataRecordsAsCSV" activity for Export to Excel. In order to support the export of summarized columns in Report Definition, an enhancement has been added that uses the column label as an alias for aggregate fields in the native SQL builder of the exportData API to form a map between the property name and the alias name and use it while iterating over the result set.

SR-B41433 · Issue 297836

BIX documentation updated for ExtractDataWith Args

Resolved in Pega Version 7.3

The BIX User Guide has been updated to describe how one should pass arguments when using pxExtractDataWithArgs.

SR-B44199 · Issue 300058

Fixed Access Control Policy in Assign- classes

Resolved in Pega Version 7.3

An error was generated when attempting to create an Access Control Policy in Assign- classes. This was due to a missing use-case, and has been corrected.

SR-B44199 · Issue 299984

Fixed Access Control Policy in Assign- classes

Resolved in Pega Version 7.3

An error was generated when attempting to create an Access Control Policy in Assign- classes. This was due to a missing use-case, and has been corrected.

SR-B44199 · Issue 297134

Fixed Access Control Policy in Assign- classes

Resolved in Pega Version 7.3

An error was generated when attempting to create an Access Control Policy in Assign- classes. This was due to a missing use-case, and has been corrected.

SR-D33832 · Issue 503957

Configurability added to SLA Timeliness to allow either 0 or NULL for Unqualified records

Resolved in Pega Version 8.2.4

When using a Report Definition where the count (aggregate function) was used for both the WithinSLA and Past Deadline columns, the correct value was not getting displayed. The correct value was displayed when the sum function was used instead of the count function, but clicking 'value' returned all values despite what value was displayed on the screen. This was a behavior change related to performing a drill down action on a report definition. As per the older behavior, drill down relies on a specific value (NULL) to determine whether a record is a candidate to be shown in the drill down report. From 7.2.1 forward, drilldown relies on value 0 instead of NULL to make the average summarize function work properly, which led to a change in behavior when used with other summarize functions like sum and count. To resolve this, SLA Timeliness related RAFs have been modified to conditionally return either 0 or NULL for Unqualified records based on a DASS config.

SR-D15822 · Issue 485162

PageList under PageGroup Repeating Layout corrected

Resolved in Pega Version 8.3

An issue with the PageList under PageGroup Repeating Layout not working has been resolved by modifying the system so the initial "." will not be removed when using a page from a property. In addition, the newRow functionality has been updated to support the use of an embedded pagelist in a page list.

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