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-A204 · Issue 205451

Resolved sporadic NPE on TransferAssignment

Resolved in Pega Version 7.1.9

A null pointer exception was sporadically being being generated by the pxTransferAssignment activity. This was found to be an issue where a previous step to open the work object failed and the TransferWorkPage was therefore not created, followed by the absence of that page leading to the failure of the WHEN condition that was using the Rule-Utility-Function hasMessages. The handling has been updated to avoid this issue.

SR-A2047 · Issue 205630

Resolved AddWorkHistory length error

Resolved in Pega Version 7.1.9

The "AddWorkHistory? activity was generating an error when the property pyInstructions contained more than 64 characters and was copied into pyLabel without taking care of the length restrictions imposed on these properties. This has been resolved by implementing the required length restrictions before copying.

SR-A2353 · Issue 206676

Adjusted process timing to address resolve error

Resolved in Pega Version 7.1.9

When a Payment case created as the child of a Supplier claim case was resolved, a processing error was generated. This was traced to a timing issue where the Resolve activity removed pyWorkCover from the clipboard before the Supplier Claim Wait assignment was fully completed. A check has been added to ensure necessary elements have been passed before clearing the clipboard.

SR-A2425 · Issue 209338

Improved RD requestor response time

Resolved in Pega Version 7.1.9

D_ManagerWorkGroups is loaded using Report Definition. Some installations were reporting an excessive load time due to referring data page activity; to improve performance, the extra processing has been moved to post activity.

SR-A3072 · Issue 206962

Attachment visibility fixed for mobile devices

Resolved in Pega Version 7.1.9

When attachments were uploaded to a mobile device, they were not immediately visible and required a refresh to be displayed. This was found to be an issue in the signature control and Attach content control where the data page referred to in the attachments display was not removed when a new attachment is added. For this release, the data page removal part has been moved to the saveattachment activity. In the next release, all attachment controls will call an API designed for that purpose.

SR-A3670 · Issue 207984

Added trim function for Operator full names exceeding max length

Resolved in Pega Version 7.1.9

If an OperatorID has a full name that exceeded 64 characters, the error ".pyWorkParty(Creator).pyLabel: "Ms [-------------------Operator Full Name--------------]" is too long, maximum length allowed is 64" appeared. To avoid this issue, the pyLabel will trim the full name to 63 characters.

SR-A3773 · Issue 210780

SLA rule form corrected to allow 3 digits in days field

Resolved in Pega Version 7.1.9

Due to an error, the SLA rule form had a limitation of 2 characters for entering the number of days for goal/deadline/passed deadline options. This has been corrected.

SR-A3870 · Issue 211373

Localization added for Field value pySameAsCurrentStage

Resolved in Pega Version 7.1.9

Localization has been added for the Field value pySameAsCurrentStage.

SR-A4227 · Issue 209904

Fixed History-Add API error

Resolved in Pega Version 7.1.9

Within a For loop calling History-Add to add Audit information resulted in the error: "Class not defined in dictionary: History-Code-Pega-List. Details: Invalid value for aClassname passed to .createPage" . This was caused by an incomplete implementation of the function; when History-Add method is called in the method generation for an embedded page, context is switched to the Top Level Page, but when the Top Level Page is Code-Pega-List the current page context is used. This context was not correctly reflected in the History-Add function, and has been fixed.

SR-A4261 · Issue 211712

XSS security updated for LoadPulseImage

Resolved in Pega Version 7.1.9

XSS vulnerability handling has been added to the pzLoadPulseImage control.

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