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-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.

INC-207218 · Issue 706369

Check added to prevent duplicate approval by single agent

Resolved in Pega Version 8.6.4

When using a cascading Approvals process supported both by a web access button or by responding via email, a single agent could use both methods and advance a case an additional step as if they were the next approval level. This was due to the system only checking the pzInsKey when processing the approval while the assignment key will be the same for the cascading approvals assignments. This has been resolved by introducing a datetime check to validate if the email approval assignment creation datetime and the one in the database have same value; if yes the approval process will proceed and if not it will exit.

INC-207320 · Issue 701082

Email Approver shown in audit

Resolved in Pega Version 8.6.4

Email Approver activity was not being shown in Audit. This was traced to the queue instance primary page missing the necessary pyInboundEmail page property from pyCreateAndManageWorkFromEmail, and has been resolved by updating the listener activity to copy the needed value to a property called pyEmailFrom which will be used to record the events in the audit.

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