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-D40599 · Issue 508279

Handlign added for Japanese half-space character during DB query

Resolved in Pega Version 8.3.1

After creating a Report Definition based on the Unicode/Japanese text property with summary list, the list was visible from Report viewer but any full size space used by the summary filter was unintentionally trimmed to half size space. As a result, the database query could not find the item. This has been resolved by modifying the setGroupByInputs API in the pega_report_summary js file to use the unicode space char(\u0020) instead of \s in regex. The Japanese space character will be replaced in the pzDrillDownReport activity step 2 for the query use, and will be set back to the Japanese space character in pyFilterValue.

SR-D42138 · Issue 509288

Fixed white space issues with Previous and Next buttons in multi-page Audit Reports

Resolved in Pega Version 8.3.1

After upgrade, multiple-page Audit Reports in GOC had too much white space between the end of the numbers and the Next Button, and the Previous Button had too much white space between 'Previous' and the start of the numbers. This was traced to a coding error in the pzbase-browser CSS generation that resulted in a space between "div" and "[node_name="pyGridPaginator"]". This has been fixed. Unused webkit selectors have also been removed.

SR-D17306 · Issue 490918

RD pagination expanded to 1500 rows

Resolved in Pega Version 8.3.1

The default pagination enabled on the Report Definition was limiting the results to 50. This has been enhanced to a row limit of 1500 in report definitions pzGetAllPropertiesOfGivenClass.

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