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.

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.

SR-A4308 · Issue 211808

Corrected revalidateAndSave modifying the 'Applies to' class

Resolved in Pega Version 7.1.9

During upgrade, revalidateAndSave was modifying the 'Applies to' class of the included rule. The issue was caused by modification of the pyIncludedRuleXML in the flow action / section rules that holds the included section's information; flow action was depending on this page to set the class, but since this page no longer existed the class was defaulting to the current flow action's primary class. To resolve this, if pyPrompt class is blank in activity Rule-Obj-FlowAction.OpenDefaults, the system will try to get the page name from the flow action rule, iterate across its pages and classes, and find the class name where the page name matches and set that as the applies to class for the flow action's section.

SR-A4840 · Issue 212310

Resolved privilege issue for Attach Rule

Resolved in Pega Version 7.1.9

A RuleNotFound error was generated if a 'when' rule was part of a custom attachment category rule (specified for access control) and there was an attempt to add an attachment when the WO was opened in Review mode or if an attachment was being added to a resolved WO. Due to the error, the customer category was not then available in the category drop down list. This was due to GetListOfAttachmentCategories referring to newAssignPage to get the reference page and failing the privilege check. This has been resolved by updating the steps to default to pyWorkPage for the local variable.

SR-A4940 · Issue 211386

Improved performance for large History-Work reports

Resolved in Pega Version 7.1.9

When History-Work- contained a very large number of rows, performance issues were seen while running the History-Work-.pyGetStatusChanges report. To resolve this, the RD History-Work-.pyGetStatusChanges has been updated with modified filtering conditions and improved error handling for blank param.InsKey fields.

SR-A5054 · Issue 211505

Corrected revalidateAndSave modifying the 'Applies to' class

Resolved in Pega Version 7.1.9

During upgrade, revalidateAndSave was modifying the 'Applies to' class of the included rule. The issue was caused by modification of the pyIncludedRuleXML in the flow action / section rules that holds the included section's information; flow action was depending on this page to set the class, but since this page no longer existed the class was defaulting to the current flow action's primary class. To resolve this, if pyPrompt class is blank in activity Rule-Obj-FlowAction.OpenDefaults, the system will try to get the page name from the flow action rule, iterate across its pages and classes, and find the class name where the page name matches and set that as the applies to class for the flow action's section.

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