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.

INC-184729 · Issue 669740

Pinning document to space correctly generates thumbnail

Resolved in Pega Version 8.6.2

When pinning a document to a space using the standard document repository tile, the resulting pin did not have an image corresponding to it. The process worked properly when pinning a document directly from the space itself. This was a missed use case and has been resolved by adding an update to set the pyImage of the document while pinning the space.

INC-185950 · Issue 669194

Withdraw task notification uses correct email sender

Resolved in Pega Version 8.6.2

When withdrawing a Task, the withdraw email was sent from the default email box instead of the expected Application default email box. This was traced to the 'pyTaskDeleted' (notification name for withdraw task) value not being present, which meant the system fell back to the task 'pyTaskAssigned' notification name. To resolve this, an update has been made to have pyIsPulseNotificationDefinition return true for a pyTaskDeleted notification.

INC-186489 · Issue 668372

Offline mobile app create work with parameters correctly saves work object

Resolved in Pega Version 8.6.2

The CreateNewWork processor was not saving the work object after merging client and server page. This has been resolved.

INC-163914 · Issue 668845

Improved Agile Studio passivation recovery

Resolved in Pega Version 8.6.2

When an Agile Studio session was passivated, the error "SECU0008 : CSRF Detected and Blocked" was seen. Reactivating the session resulted in a blank page. This was traced to the clearing of requestor level registrations added for that particular thread, and has been resolved by adding a new flag to identify if a thread is passivated along with the necessary structure for the conditionalized clearing of requestor level registrations based on this flag.

INC-179360 · Issue 662177

Check added for allowed editing with CSRF

Resolved in Pega Version 8.6.2

After enabling CSRF, it was not possible to edit a data table used to define ACL rules due to security preventing the adding/editing of rows and user group entitlements. This has been resolved by using browser FingerPrint validation to check whether an activity is in a secured list and skipping validation for allowed activities.

INC-180275 · Issue 666455

Collaboration control hidden if data type is delegated

Resolved in Pega Version 8.6.2

When collaborating using a customized CaseManager portal with some delegated data types, the admin user refreshing the Data Type view changed the collaborator's view from the portal to show the Data Type tabs, allowing the second person to open rules (properties, Data Pages, etc) and see the configuration even though they could not make any changes. This has been resolved by updating pzDataTypeDelegated to display the collaboration control only if pzDelegation is false.

INC-180594 · Issue 670955

Filtering added for DisableDormantOperators

Resolved in Pega Version 8.6.2

When running the Disable Dormant Operators agent, many operators were seen which were dormant but not disabled. Investigation showed the activity was fetching all of the operators without filtering the deactivation state. This has been resolved by adding a filter condition in pzDisableDormantOperators to fetch only deactivate state users.

INC-184804 · Issue 669638

Password security enhanced

Resolved in Pega Version 8.6.2

Security and authentication have been enhanced for password handling.

INC-185362 · Issue 668825

Keystore update properly revises the cache

Resolved in Pega Version 8.6.2

A keystore updated with the latest certificate was not getting reflected in the runtime and the old certificate was getting picked. In a multi-node environment when the new JKS is uploaded in one node, the changes are expected to be communicated to other nodes so that the cache can be cleaned up. In this case, investigation showed that the keystore label was in uppercase and the cache entry was not correctly removed. This has been resolved by adding an update that will convert the cache key to lowercase and maintain uniformity to ensure proper cleanup.

INC-186512 · Issue 669327

Password security enhanced

Resolved in Pega Version 8.6.2

Security and authentication have been enhanced for password handling.

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