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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-B81382 · Issue 339184

Fixed intermittent Robot Manager exclusion

Resolved in Pega Version 7.4

A robot was successfully registering from Pega Robotics to Pega Platform (based on Pega Robotics logs and successful retrieval of cases), but the robot was intermittently not shown on the Robot Manager. This was due to the operator inheriting the the class "History-Data-Admin-Operator-ID" without using the field 'Label'. Since the RD 'pzGetRobotFailedAssignmentCount' created to fetch all the descendent class instances was now missing a mandatory field, the RD did not fetch the results at all. To resolve this, the option "report on Descendent class instances" has been unchecked in the RD 'pzGetRobotFailedAssignmentCount'.

SR-B81510 · Issue 335028

Support added for multi-byte character sets in RD filters

Resolved in Pega Version 7.4

In order to support Report Definition Filters for multi-byte characters such as Chinese script, the code has been updated so the filters flow will set the prepared value corresponding to a NVARCHAR type column.

SR-B81510 · Issue 335031

Support added for multi-byte character sets in RD filters

Resolved in Pega Version 7.4

In order to support Report Definition Filters for multi-byte characters such as Chinese script, the code has been updated so the filters flow will set the prepared value corresponding to a NVARCHAR type column.

SR-B84727 · Issue 334532

Index-Agents table max removed

Resolved in Pega Version 7.4

The Agent Management Landing page in Designer Studio was not displaying all of the agents that were configured in the cluster due to the Index-Agents table exceeding the 500 result limit imposed by the report definition Index-Agents.pzGetAgents. To better support large installations, the RD configuration pyMaxRecords has been changed to 0 so it will retrieve as many records as are present in the DB.

SR-B84752 · Issue 337830

Fusion charts respect 0 decimal place setting

Resolved in Pega Version 7.4

The fusion chart was not dividing the axis as a whole number even thought the decimals were set to 0. This has been fixed by modifying the pzNumberFormatting XML stream to set the default values for AxisMaxValue to 2 and numDivLines to 1 on chart config in cases where decimals is set to 0.

SR-B84765 · Issue 341704

Fixed VirtualList RD content display

Resolved in Pega Version 7.4

When a complex reference with more than 3 levels depth was used in the select fields of report and the complex reference contained an auto-populate page property with its key as one of the properties within the page itself, VirtualList failed to populate featureProperty and no data was displayed. This was traced to two issues: first, the decorateSingleFrame API was trying to fetch the VirtualClipboardProperty from VirtualClipboardPage using a complex reference which resulted in NullPointerException. Because of this exception, featureProperty was not set and the auto-chain was broken. Second, the iteration logic used to iterate through the complex reference was incorrect. These have been fixed.

SR-B84879 · Issue 339472

Circumstanced RD 'save as' works

Resolved in Pega Version 7.4

In portal, it was not possible to use 'save as' on a Report Definition which was circumstanced. This was because performing a save as on a report from the report viewer put the copy in the first unlocked ruleset. If the report was circumstanced, the copy would be also. This can cause errors if the rule would not be valid in the new rule set (for example, the base version of the rule may not be present). In order to allow 'save as', a step has been added to pzRRSaveAS which will remove the circumstance properties from the report definition primary page.

SR-B85544 · Issue 337433

Fixed RD fail for Japanese characters

Resolved in Pega Version 7.4

Report definition was failing when the Class name contained Japanese characters. This was an issue with the use of default encoding (now deprecated) and an update has been made to ensure the use of 'UTF-8' encoding for URLs.

SR-B85885 · Issue 336053

PDF images exported

Resolved in Pega Version 7.4

On adding an image to a report and exporting it, the image was not getting exported to PDF. This was caused by the header section pzDisplayReportSectionForPDF is final, and it has now been made available to extend and modify.

SR-B87507 · Issue 335843

Localization added to Chart messages

Resolved in Pega Version 7.4

Chart messages have been localized in the Cases by Status widget.

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