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-C77533 · Issue 416618

Added null check for ApprovalFlowName in pre-processing activity of "pzApprovalPreProcessing"

Resolved in Pega Version 8.1.3

When a "pyApproval" flow action was configured in one of the assignments of a case Type for Approval action by the manager, the error message "The Flow Action pre-processing activity pzApprovalPreProcessing failed: The reference .pxFlow().pyFlowParameters.pyApprovalSectionName is not valid. Reason: Empty subscripts are not valid for the element : pxFlow" appeared when the Approval section was displayed. To correct this, a null check has been added for an empty ApprovalFlowName in step 1's second property set and transition step.

INC-223074 · Issue 720454

Fallback handling improved for import synchronization

Resolved in Pega Version 8.8

Upgrade to CRM 8.7 was failing during the import of the CRM jar. There are some rare edge cases where instances may be in the database, but not visible to the engine until the import is already underway, such as when rollback has deleted a class definition and mapping but not the instances of the class itself. To mitigate the risk of PK constraint violations when this happens, the process has been modified to mark all the instances that cannot be directly synchronized as updates so that the data layer will upsert them.

INC-212966 · Issue 713956

Support added for email attachments stored in repositories

Resolved in Pega Version 8.8

Attachments sent through email were received as corrupted. To resolve this, support has been added for retrieving content attachment file content from external repositories using data page D_pzGetExtStorageContent[ContentLocation:.pyContentLocation,RepositoryName:.pyStoredInRepository].pyFileSource

INC-234503 · Issue 745906

Corrected PrimaryTopic detection

Resolved in Pega Version 8.8

Using natural language processing (NLP) to detect a topic worked as expected, but the list in the clipboard was unordered and an incorrect value was set as the primary topic. This was traced to the system not sorting pyTopics after aggregating the topics from the body and attachments, and has been corrected.

INC-234290 · Issue 742941

Conversational Channel training model documentation updated

Resolved in Pega Version 8.8

Documentation for Conversational Channels has been updated with additional information about the process of creating training data based on CSR actions such as 'create a case' or 'send a reply using suggested/other replies'.

INC-201219 · Issue 696610

Updated chart button markup

Resolved in Pega Version 8.8

Some of the buttons were incorrectly displayed while clicking "Edit Report" from the Cosmos report browser. This was due to the buttons generating markup that was used to support older browsers in pzChartButtons, and has been resolved by updating the button markup.

INC-190053 · Issue 680232

Mobile attachment count corrected

Resolved in Pega Version 8.8

Parametrized data pages were not being populated as expected, causing an incorrect attachment count when opening a case in Mobile. This has been corrected.

SR-C78352 · Issue 417618

Transform on an onclick event refresh added to DT

Resolved in Pega Version 8.1.3

When calling the refresh method, the transform on a onclick event refresh was not invoked. Support for this refreshSection action has been added for running data transform and activity.

INC-191371 · Issue 684481

Security update for GetAssignmentDetailsInternal errors

Resolved in Pega Version 8.8

Error handling for pzGetAssignmentDetailsInternal has been updated to return a 403 (forbidden) HTTP status code in place of potentially sensitive information when access is denied.

INC-192935 · Issue 688463

Added deferred loading for email cases

Resolved in Pega Version 8.8

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