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-203595 · Issue 700595

Updated retainLock for DoClose activity

Resolved in Pega Version 8.7.1

After sending an external email notification from a case, attempting to use the "close" button resulted in an access denied error. This was traced to a missed use case for recent security improvements which resulted in not setting the required parameter retainLock for the DoClose activity, and has been resolved.

INC-204676 · Issue 699112

Localization added to subject line for SendEmailToAssigneeOnGoalTime

Resolved in Pega Version 8.7.1

When a Callback case was created and the assignee notified by email, the subject line was not localized. This has been corrected.

INC-207320 · Issue 701083

Email Approver shown in audit

Resolved in Pega Version 8.7.1

Email Approver activity was not being shown in Audit. This was traced to the queue instance primary page missing the necessary pyInboundEmail page property from pyCreateAndManageWorkFromEmail, and has been resolved by updating the listener activity to copy the needed value to a property called pyEmailFrom which will be used to record the events in the audit.

INC-183706 · Issue 685830

Added null check for DynamicAppenders

Resolved in Pega Version 8.7.1

Null pointer exceptions were seen for Pulse. This has been resolved by adding a null check in the DSS save/update process.

INC-185117 · Issue 680899

Check added to disable offset support for older versions of Oracle

Resolved in Pega Version 8.7.1

An ORA-00933 error was generated after upgrading from Pega 7.1 to Pega 8.5. This was traced to a conflict between Oracle 11g and the Pega 8.5 platform related to an OFFSET statement being added to a query for a version of Oracle that doesn't support it. The preferred solution is to upgrade Oracle to address this, but in order to support backwards compatibility a check has been added which will disable offset support in Oracle if productversion <=11.

INC-202677 · Issue 698989

Handling added for missing expose.accessGroup property

Resolved in Pega Version 8.7.1

After exposing an existing page group and page list properties along with single value properties using a declare index, running the Column Populator tool prpcServiceUtils to populate the historical data resulted in the single value properties being updated in the exposed column properly, but the page group and page list properties were not updated in the declare index table. On new case creation the declare index tables were updated. This was traced to the default expose.accessGroup not being set for the user, and has been resolved by adding a check and handling that will add the missing property in prpcserviceutils.properties defining the access group for the Rule-Declare-Index of the classes being exposed if it is not present.

INC-192935 · Issue 698695

Inline images retrieved for deferred-load email

Resolved in Pega Version 8.7.1

When emails were defer-loaded, inline images with code entered into the non-cache section in pyExtractHtmlFromAttachment were not being displayed. This has been resolved by passing the current page parameter to pyExtractHTMLFromAttachment to convey the pyID.

INC-200148 · Issue 693148

Added JSoup handling for older Microsoft Outlook versions

Resolved in Pega Version 8.7.1

Logging indicated that some emails were generating the error "pyextractlatestreplyfromhtml is resulting in java.lang.IllegalArgumentException: Object must not be null." This occurred when using an older version of Microsoft Outlook, and has been resolved by adding a check before removing the JSoup doc object.

INC-200237 · Issue 693179

Added API for Pega Call Team websocket reconnect

Resolved in Pega Version 8.7.1

When a call came in, the operator was not able to pick it up due to the popup only containing a reconnect section. This has been resolved by adding the disconnectAndReconnect API which will be used by Pega Call Team if the websocket reconnect limit exceeds 5.

INC-203463 · Issue 694163

Added deferred loading for email cases

Resolved in Pega Version 8.7.1

When there were a significant number of email interactions on an email case, delays were seen when loading the case in the UI. Investigation traced this to a high number of database calls along with the BLOBs also being open. To improve performance, the new rule pyDeferLoadEmails has been added which toggles the UI and loads emails faster. In addition, the button label has been modified to read "View all emails" in place of "Show all" while defer load is enabled.

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