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-B38578 · Issue 272419

Fixed null-pointer exception in external DB extract

Resolved in Pega Version 7.3

When using a class which maps to a table in an external database, running an extract caused a database permission error when trying to access the pr_log table in the PegaRULES database. This exception was caught and logged but then processing continued, resulting in a NullPointerException being thrown. To correct this, the sequence number generator has been modified to use the pr_log table instead of the class on which extract is defined.

SR-B39476 · Issue 297525

addCalendar() RUF logic updated

Resolved in Pega Version 7.3

The addCalendar() RUF logic has been modified to correctly set the operator time zone and correctly add the given years, months, days etc. This fix will be active based on a DASS setting as addCalendar() cannot be directly changed due to backward compatibility with DateTime issues.

SR-B39528 · Issue 303927

Node startup modified to support very large clusters

Resolved in Pega Version 7.3

Node startup was failing if the cluster had more than 50 nodes. This issue was caused by the query to the "pr_sys_statusnodes" table only returning 50 records; this limitation has been removed.

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

SR-B42581 · Issue 299511

BIX enhancement to handle unaligned external mappings

Resolved in Pega Version 7.3

If a class with external mappings was configured and some of the properties did not match the db column name, a filter for one of those properties would not be applied to the extract query. In order to support business needs that contain the mis-match, an enhancement has been made to the BIX code to handle this non-alignment.

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