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-154564 · Issue 617350

JAWS reads the table header and filter options separately

Resolved in Pega Version 8.4.4

When table headers for a non-optimized table with filter options received focus in Google Chrome, JAWS read the header, sort and filter options all run together. This was due to a difference in the way JAWS reads headers in Google Chrome from the way it reads them in IE, and has been resolved.

INC-154680 · Issue 619027

Moment timezone library update

Resolved in Pega Version 8.4.4

In order to reflect updates such as Brazil discontinuing DST time, the moment timezone libraries have been updated to the latest available version.

INC-154855 · Issue 616002

Updated expression handling when not using client side validation

Resolved in Pega Version 8.4.4

After upgrade, a declare expression used to calculate the end date when creating a schedule case was not populating the result. This was traced to a missed use case for evaluating expressions when 'Enable client side validation' is unchecked, and has been resolved.

INC-156992 · Issue 619707

Show-stream/html repaired for custom portals

Resolved in Pega Version 8.4.4

After upgrade, show-stream/html in activity was not getting executed properly on custom portals. ShowDesktop was modified in 8.1 for AssociateRequestor implementation. As part of that, the custom portal step was moved to the new activity pzPopulateRequestor which is invoked from ShowDesktop. The JUMP condition in step is exiting the pzPopulateRequestor activity, but not ShowDesktop as was the case in the previous versions. To resolve this, the JUMP condition (.pyDesktopType=="Custom") has been added in ShowDesktop at the pzPopulateRequestor call step.

SR-69015 · Issue 619995

Unescaping characters implemented for expressions

Resolved in Pega Version 8.3.6, Resolved in Pega Version 8.4.4, Resolved in Pega Version 8.5.3, Resolved in Pega Version 8.6

An issue where expression builder statements were evaluated differently at runtime than at testing has been resolved. Pega Platform expressions with String literals(that is, sequences of characters enclosed in quotation marks) now unescape characters in strategy shapes such as Set Property or Filter.

INC-188469 · Issue 714844

Updated retainLock for DoClose activity

Resolved in Pega Version 8.6.5

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-208394 · Issue 713554

Error handling updated for Data-Work-Attach-File

Resolved in Pega Version 8.6.5

If a file is uploaded which has the same name as an existing case attachment or if any issue happens during file attachment, the attachment will fail and an error message is displayed with an option to cancel the operation. However, even if the upload was not successful the related Data-WorkAttach-File instance was created and persisted in the Workattach table. Investigation showed this was caused by the process for persisting the Data-WorkAttach-File record occurring prior to the process that returns the errors, and this has been resolved.

INC-209404 · Issue 710406

MultiFilePath supports file upload with leading special character

Resolved in Pega Version 8.6.5

Updates have been made to the pzMultiFilePath control in order to support uploading a file with a special character such as "%" at the beginning of the name.

INC-210787 · Issue 710393

Multiple child case assignments open correctly in Ajax container

Resolved in Pega Version 8.6.5

After configuring two cases with a parent-child relationship, the child case was configured with a parallel process with two assignments. When trying to open the child case assignments in an Ajax container, only the first assignment would open. Investigation showed this was caused by the "reloadAlways" parameter not being sent to openAssignment due to a custom control being used. To resolve this, the reloadAlways has been added as an argument to the OpenAssignment function call in pyAssignmentsLabel.

INC-213654 · Issue 726002

Logic added to skip FLAudit class during compliance check

Resolved in Pega Version 8.6.5

An application compliance error was seen related to classes starting with FLAudit, which are created as part of field level audit history for the classgroup validation. This has been resolved by adding an extra condition to the Rule-Obj-Class-.Validate activity to check if inheritance is from "FLAudit-" class, and if so to skip them as their purpose is similar to History- classes which are ignored for the class group validation.

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