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-B40665 · Issue 302272

Update to avoid unnecessary File Listener logging

Resolved in Pega Version 7.3

After upgrade, occasional errors were appearing in the log files while the listener was running correctly and files were being successfully processed. This was traced to the authentication privileges method encountering a service type that was not set, causing the class Rule-Service-null to be created. To avoid the unnecessary logging, code has been added to set service type in case of File Listener.

SR-B40706 · Issue 297501

Unmapped columns from an external table skipped in DDL query generation.

Resolved in Pega Version 7.3

The OBJ-SAVE method was generating a query in which unmapped columns were also getting updated. As these columns were not mapped, DB columns were being updated with the value NULL. This was due to the Obj-Save function always saving the entire object, causing an issue when only part of a table is mapped to a class. To correct this, new prconfig and DASS settings have been added to exclude unmapped columns of an external table as part of DDL query generation.

SR-B40734 · Issue 297396

Facebook Connector queries updated

Resolved in Pega Version 7.3

The default queries used to harvest private messages in Facebook Connector have been updated to match changes made by Facebook.

SR-B40783 · Issue 297484

Fixed value focus for percentage control in repeat grid

Resolved in Pega Version 7.3

When configuring percentage control with integer type property inside the Repeat Grid, the field displayed the Case ID and some text instead of the value when focus was out. This was due to an empty string being passed, and has been corrected.

SR-B40812 · Issue 304049

New section made available for customized RB report generation date

Resolved in Pega Version 7.3

In order to support customized formats in the generated date used by Report Browser, the new section PYDISPLAYREPORTGENERATEDDATETIME has been made available. This is accessed through pzDisplayReportSectionForPDF, and replaces the "generated on" datetime property used previously.

SR-B40923 · Issue 297879

Removed extra File Listener logging

Resolved in Pega Version 7.3

After upgrade, an INFO entry appeared in the logs every time the file listener processed a file. To correct this, the log statements level has been changed From infoForced to debug.

SR-B41030 · Issue 298187

Branch Merge Wizard shows up to 200 ruleset versions

Resolved in Pega Version 7.3

In the rule:pzGetVersionsForMerge List View, the page size has been changed from the previous limit of 50 to the new value of 200.

SR-B41106 · Issue 298379

Bulk process with only 'case type any' properly assigns all processes

Resolved in Pega Version 7.3

When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.

SR-B41140 · Issue 300825

Fixed column alignment in progressive repeat grid

Resolved in Pega Version 7.3

The scrollhead th was generated even when there was no scrollbar for a fixed header grid, causing the column alignment of records in a repeat grid with Progressive pagination that contained one or two rows to become progressively more disaligned from the column headers. The problem did not appear if the actual number of rows was equal to the page size. To fix this, the system has been updated to not generate the scrollhead th when the number of rows is less than the page size of the grid.

SR-B41398 · Issue 303897

Improved exception handling for "reset logging to default"

Resolved in Pega Version 7.3

After enabling debug level logging to a file, clicking "Reset all loggers to default settings" did not actually do so despite presenting a confirmation message. This was traced to incorrect handling for an exception, and has been fixed.

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