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.

INC-184526 · Issue 668848

Updated audit history for archived cases

Resolved in Pega Version 8.7

As part of a field level audit implementation for archival scenarios, the History messages copied information directly from the database which resulted in descriptions which were unnecessarily technical. This has now been updated to insure the technical descriptions are translated into descriptions which are more easily understood.

INC-184816 · Issue 674433

Added handling to find the workparty for FixCorrespondence

Resolved in Pega Version 8.7

Using a Send Email smart shape and triggering email by passing the target email ID instead of the workparty role triggered the email as expected, but if a fix correspondence flow was initiated due to some error during the transaction, it was not possible to resubmit the fix flow action. Investigation showed that this was due to the fix correspondence flow check using the party role, which had not been passed. This has been resolved by updating the corrUpdate and createAndProcessCorr activities to copy the pyCorrPage from NotifyOp which contains the getgetEmailSenderInfo and use it to set pyCorrPage.pyStreamType.

INC-186654 · Issue 669115

GetStatusChanges performance improvements

Resolved in Pega Version 8.7

Performance issues were seen when running the GetStatusChanges report. This was traced to the filtering methods used, and has been resolved by updating the report definition and enhancing the filtering conditions.

INC-186868 · Issue 675245

Security updated to allow Access group switching

Resolved in Pega Version 8.7

When a member of two different access groups attempted to switch from one group to another, an "access denied" message occurred. This was traced to the use of BAC, and has been resolved by updating the pzProcessApplicationSwitch activity to use the pzEncryptURLActionString function to register the request.

INC-188678 · Issue 672977

CheckFlowDependencies query performance improved

Resolved in Pega Version 8.7

In order to improve performance on very large tables, the pxCheckFlowDependencies activity has been modified. Previously, checking whether a dependency exists retrieved all columns. The updated query will instead return a count.

INC-189622 · Issue 682098

Cleaned up references to deprecated property type

Resolved in Pega Version 8.7

While using the Pega API to update a case from one application to another, an error was generated indicating the system was unable to find a property definition of “caseTypeClass” in pyAddableWorkList of the workpage. All properties in the clipboard pages of the work page are validated during this update: in this case, the check was for the caseTypeClass property, which is no longer used but which was on the clipboard page. To resolve this error, all remaining references to property casetypeclass have been removed.

INC-190819 · Issue 681999

Wrapper added to set correct bulk transfer context

Resolved in Pega Version 8.7

Bulk transfer was not working as expected when transferring an assignment from a flow defined in data class. Investigation showed the bulk transfer UI was getting picked from work- class while the post processing was running under data class context: this has been resolved by creating a wrapper activity in baseclass to call the post processing activity Work- .

INC-191645 · Issue 679536

Updated FieldLevelAuditing logic for page comparison

Resolved in Pega Version 8.7

Optimistic locking was resulting in orphan assignments and the error "Error: Flow Not At Task, Error: Flow Removed". In addition, Get Next Work was causing duplicate Field Level Auditing records. This was traced to a missed use case in the logic used in pxFieldLevelAuditing where previousPage and PrimaryPage are compared to see whether they are equal or not, and has been resolved by adding one more condition to mark previousPage as null when the update date time or commit date time are not updated as part of processing.

INC-192979 · Issue 677696

Case creation and Save As performance improvements

Resolved in Pega Version 8.7

Performance improvements have been made to the getApplicationRuleSetList() function to avoid unnecessary and repetitive database calls.

INC-194429 · Issue 682882

Updated FieldLevelAuditing logic for page comparison

Resolved in Pega Version 8.7

Optimistic locking was resulting in orphan assignments and the error "Error: Flow Not At Task, Error: Flow Removed". In addition, Get Next Work was causing duplicate Field Level Auditing records. This was traced to a missed use case in the logic used in pxFieldLevelAuditing where previousPage and PrimaryPage are compared to see whether they are equal or not, and has been resolved by adding one more condition to mark previousPage as null when the update date time or commit date time are not updated as part of processing.

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