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-184040 · Issue 688255

Improved accessibility for Disclosable Documents/attach files/auto selection dropdowns

Resolved in Pega Version 8.6.4

When using Dragon for accessibility, issues were seen when trying to select different options in the dropdowns related to attaching multiple files. This was caused by the legacy grids being used not supporting this type of accessibility functionality, and has been resolved by updating pzAttachFileDDFileList to use an optimized table instead.

INC-187350 · Issue 703198

UUID added to iOS direct photo upload to differentiate filename

Resolved in Pega Version 8.6.4

When "Content Storage" with the option "Store in repository" was enabled on the "Integration" tab in the Application definition, it was not possible to add more that two attachments to a case with an iPhone when directly capturing a photo through the camera app instead of uploading the photo as an attachment using the gallery. When using the default "Store in Pega database", the additional photos could be uploaded directly from an iOS camera without any errors. Investigation showed that when "Store in repository" was enabled, a file name conflict check was done in the repository. Because the iOS camera app saves/uploads every image as "image.jpg", this caused the error when checking for a filename conflict in the repository. This has been resolved by adding code to append a UUID to the attachname when the device is mobile and browser is Apple Safari.

INC-192673 · Issue 689554

Tab highlighting updated

Resolved in Pega Version 8.6.4

Not all elements were indicated with yellow highlighting when tabbing through the screen. This has been resolved.

INC-194180 · Issue 704638

GetChildcases handling updated for large numbers of cases

Resolved in Pega Version 8.6.4

When a very high number of child cases being processed contained a wait shape that was dependent on the movement of a parent case, some of the cases were moved to the next step of the flow automatically while others required a manual command to ResumeFlow. In extreme cases where many child cases were waiting, a node crash could occur. This was traced to the pzGetChildcases report having a maximum value of 500 lines, and has been resolved by increasing the maximum number of rows to retrieve to 9999 in the Data Access Tab of the pzGetChildCases report definition. In addition, the pxCheckFlowDependencies activity has been modified to perform with a higher number of cases, and DSS(MaxRecords) logic has been added to split the child cases into multiple queue items for each access group to decrease load on each thread process.

INC-198765 · Issue 696680

Public URL will be appended with "/" if it is not present

Resolved in Pega Version 8.6.4

When using the Worklink Correspondence Fragment rule with authentication service type "prweb/PRAuth/sso", the returned URL did not contain the needed "/" at the end of public link. The "/" was present when using the legacy authentication service "prweb/sso". This has been resolved by updating the system to include a "/" at the end of a public URL if one is not present.

INC-200247 · Issue 701954

WorkAttachmentIcon activity correctly registered

Resolved in Pega Version 8.6.4

The pyWorkAttachmentIcon control used to download attachments was generating a SECU0019 warning. This was traced to pzAppStorageOkToAttachFile not being correctly registered, and has been resolved.

INC-200936 · Issue 703343

SFTP support added to ValidateURL rule

Resolved in Pega Version 8.6.4

SFTP has been added to the list of schemes which are accepted as part of the validation in the pxValidateURL rule.

INC-201723 · Issue 701068

Audit message displays correct parameter value

Resolved in Pega Version 8.6.4

The Audit message showed "{1}" instead of displaying the parameter value dynamically. This was traced to the pyInstructions field value which contained the message "Please approve or reject this {1}", and has been resolved by updating the pzInstructionsForApproval rule so the correct value is displayed.

INC-203595 · Issue 700594

Updated retainLock for DoClose activity

Resolved in Pega Version 8.6.4

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-204676 · Issue 699113

Localization added to subject line for SendEmailToAssigneeOnGoalTime

Resolved in Pega Version 8.6.4

When a Callback case was created and the assignee notified by email, the subject line was not localized. This has been corrected.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us