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-B14212 · Issue 298395

Reference properties will iterate over copies to avoid conflicts with concurrent changes

Resolved in Pega Version 7.3

Concurrent Modification Exceptions were occurring in Reference Properties scenarios where backreferences were modified somewhere in the call stack while the system was looping through them. To avoid this, the system will iterate over copies of the references.

SR-B14688 · Issue 289060

Parameter added to consider production rulesets while checking rule resolution

Resolved in Pega Version 7.3

After creating a portal for admin users and adding it to a production ruleset that in turn had been added to the appropriate application and access group, adding the portal to the access group unexpectedly generated the error "Portal name: is not a Valid Record for use by this Rule." This was due to the system not considering production rulesets while checking rule resolution, and the parameter pyUserPreproductionrulesets has been added to the validate activity to handle this.

SR-B14732 · Issue 296513

Resolved error with DateTime property comparison crossing daylight savings time

Resolved in Pega Version 7.3

If an operator was using time zone "Europe/London" and locale "en_US", an error occurred when comparing two dates if the property type was DateTime and one of the dates selected in Date range fell under daylight savings time. The error did not occur if the property was of type Date. The addCalendar RUF has been updated to resolve this issue.

SR-B14732 · Issue 296847

Resolved error with DateTime property comparison crossing daylight savings time

Resolved in Pega Version 7.3

If an operator was using time zone "Europe/London" and locale "en_US", an error occurred when comparing two dates if the property type was DateTime and one of the dates selected in Date range fell under daylight savings time. The error did not occur if the property was of type Date. The addCalendar RUF has been updated to resolve this issue.

SR-B14905 · Issue 284489

Handling added for unexpected BLOB forms during multi-tenant initialization

Resolved in Pega Version 7.3

The PegaRULES engine was failing to initialize if it encountered a BLOB that was corrupt, null, empty, abruptly small sized, or less than 4 characters long when iterating through Data-Admin-Tenant records. An explicit check has been inserted to resolve this, which will throw a bad record exception with more information before trying decrypt.

SR-B15463 · Issue 287079

New Application operator mapping refinements

Resolved in Pega Version 7.3

When using the New Application Creation wizard, the newly created operators were unexpectedly mapped to the same access group even though the access groups contained different roles. This has been corrected with changes in the pxPrepareApplicationDemoUsers and pxPrepareClonedAccessGroup activities to set transient properties for the original access group name as well as for use in lookup by demonstration users.

SR-B16337 · Issue 288963

BIX TotalInserts and TotalInstance counts made consistent for nested pages

Resolved in Pega Version 7.3

The pxTotalInsertsCount and pxTotalInstanceCount values were being calculated incorrectly when using PageLists and a Page under those PageLists. This was a missed case, and the system has been updated to address it.

SR-B16825 · Issue 292599

WordMacroManagerDot updated for 64-bit compatibility

Resolved in Pega Version 7.3

The WordMacroManagerDot macro has been updated for Word-64-Bit environment compatibility.

SR-B16921 · Issue 287323

BIX documentation for Obj-Save help updated

Resolved in Pega Version 7.3

The BIX Extracts help file has been updated to clarify which properties are or are not updated when using Obj-save, explicitly noting that pxUpdateDateTime is not updated in the database when the Obj-save method is invoked and that a data transform should be applied to cause an update. Obj-save does update pxCommitDateTime.

SR-B17080 · Issue 289244

saveAllOrNone API more robust for multi-tenant shared BIX

Resolved in Pega Version 7.3

Intermittent errors appeared when two BIX command line extraction scripts were running in parallel when both used BixUser_Tenant as the operator. This was traced to the saveAllOrNone API, which was not equipped to prevent other nodes from writing data into the DB while the current thread was also trying to write that same data to the DB. Further diagnostics are required to formulate a solution to this intermittent error, but the API has been made more robust: the system will not throw an IllegalStateException when the DB exception is DuplicateKeyException.

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