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.

INC-185563 · Issue 670847

"Manage content" dialog box tab index is consistent

Resolved in Pega Version 8.4.6

The tab ordering for the "Manage content" (document upload) dialog box was not consistent. This has been resolved by updating pzModalTemplate to list the submit, cancel, etc, buttons in a consistent order.

INC-189047 · Issue 674761

Session timeout adjusted for use with Apple Safari

Resolved in Pega Version 8.4.6

A configured browser session logout timer was not working with the Apple Safari browser. This was traced to browser-specific handling for self.location.href and has been resolved by adjusting the logic and moving it inside a setTimeout to improve cross-browser compatibility.

INC-192075 · Issue 680775

Required field error message shown for Anypicker control

Resolved in Pega Version 8.4.6

Certain Anypicker controls set to required were not showing the expected error message "Value cannot be blank" in the UI when the field was submitted as blank. This has been corrected.

INC-192812 · Issue 677347

Property mapping with autocomplete control corrected

Resolved in Pega Version 8.4.6

Selecting from a list populated by autocomplete did not set the property value on property(ManagerialUserGroupLabel) which was mapped to the autocomplete control. This was traced to modifications made earlier which were intended to improve the handling for populating properties with keyboard controls, and has been resolved by reverting the previous changes. Future work is planned around the original keyboard control issue.

INC-173068 · Issue 654066

HTML tags escaped in Audit History field values

Resolved in Pega Version 8.5.6

The case narrative section was showing case statuses with encoded special characters such as % or ( ), resulting in entries such as "Status changed to Complete &# 40;approved& #41; !@##$: &#37;^& amp;*&# 40;&# 41;_&# 43;.</div>". This has been resolved by updating the PyMemo field from type Text Input to DisplayAsLiteral for case narrative, which matches the setting for case history.

INC-178650 · Issue 673547

Cross-site scripting protections updated

Resolved in Pega Version 8.5.6

Cross-site scripting protections have been updated around the DisplayAttachment function.

INC-180275 · Issue 666454

Collaboration control hidden if data type is delegated

Resolved in Pega Version 8.5.6

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-183650 · Issue 678310

Corrected doubled tag removal

Resolved in Pega Version 8.5.6

After adding two tags for a Service case, attempting to delete the first tag resulted in the second tag also being removed. When three tags were present in the case, deleting the first tag caused the first and second to be deleted. Investigation showed this was caused by the run activity pyRemoveTagLink being called twice in run time, and has been resolved by updating the run activity.

INC-183751 · Issue 665891

Improved text contrast for Attach Content button

Resolved in Pega Version 8.5.6

In order to improve accessibility, the contrast between text and background colors has been increased for the Attach Content button by updating pzMultiDragDropControlStandard to change the color from gray to black in function pzInitHTML5DD().

INC-183822 · Issue 667500

Filename with non-ASCII characters normalized for Apple Safari upload

Resolved in Pega Version 8.5.6

When using the Apple Safari browser, attaching a file name that contained Japanese characters resulted in an "attachment doesn't exist" error message when trying to open it again. This was caused by the special characters in the FileName for the Data/Query string not being encoded during the file upload, and has been resolved by updating the UploadFileToADocument activity to normalize the FileName if the Safari Browser is being used.

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