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-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.

SR-B41409 · Issue 299554

Migrated work objects properly resolve references

Resolved in Pega Version 7.3

After upgrade, Work objects created in an earlier version were not opening due to a difference in the Reference Property Link metadata used by forward links. This has been handled by ensuring the Reference Property Links are resurrected if not explicitly present.

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-B41504 · Issue 299952

Tabbed navigation research wrap-up fixed

Resolved in Pega Version 7.3

Tabbed navigation Research interaction wrap-up was displaying the review harness instead of autoclosing. In order to resolve issues with the Autoclose harness being overridden, in cases where the user is not authorized to perform the assignment AND the harness is set as "Perform", the harness purpose will be set as "Review".

SR-B41602 · Issue 300653

Filter conditions made case-insensitive for displaying column filters

Resolved in Pega Version 7.3

The filter comparator/operator dropdown was displaying different options for the same property when adding a filter for a column as opposed to dragging a property from the Data Explorer. This was caused by the dropdown logic using a case-sensitive string comparison to examine the data type of the column or filter, and has been fixed by setting the dropdown logic to ignore case when comparing the data type of the filter to determine which options are shown.

SR-B41652 · Issue 299895

createDateTimeCategories function modified to use operator time zone

Resolved in Pega Version 7.3

A report definition chart using the operator time zone of "Europe/London" and locale "en_US" displayed duplicate date columns. Updating the operator time zone to "America/New_York" removed the problem. This issue was caused by the system always parsing/formatting the date with the default local time zone, and has been resolved by modifying the parseDate/formatDate/createDateTimeCategories function to use the operator time zone instead.

SR-B41782 · Issue 297390

Improved error handling for Usage Daemon

Resolved in Pega Version 7.3

The Usage daemon was exiting due to DB error and did not recover, leading to PALSnapshotImpl multiplying and causing an OOM. This was traced to missing error handling, and UsageDaemon has now been updated to handle a DB error without exiting.

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