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-196961 · Issue 693472

Iteration method updated for SetRequiredSkillsCountColumn

Resolved in Pega Version 8.5.6

After update, database utilization spiked and did not drop. Investigation traced this to the use of Local.totalCount in pzSetRequiredSkillsCountColumn, which caused the iteration loop to run more times than necessary. This has been resolved by replacing Local.totalCount with Local.iterationsCount in the iteration.

INC-198514 · Issue 688850

CheckFlowDependencies query performance improved

Resolved in Pega Version 8.5.6

In order to improve performance on very large tables, the pxCheckFlowDependencies activity has been modified. Previously, checking whether a dependency exists retrieved all columns. The updated query will instead return a count.

INC-199880 · Issue 695068

Re-save case type completes successfully

Resolved in Pega Version 8.5.6

Checking in a case type rule with Stage Rule reference was failing. This was traced to the RuleCheckin activity being called in a nested fashion that caused an inner run to remove the "pyOriginalRecord" page which was needed in the outer run to set the .pyRuleset property (at Step 34), and has been resolved.

INC-200802 · Issue 699965

Line break handling added for setting required question asterisk

Resolved in Pega Version 8.5.6

If a survey question was formed in multiple sentences, the asterisk marking it as required was not displayed in screen. The asterisk displayed as expected if the question was one sentence. This has been resolved by updating the setMandatoryIconforQP script handle linebreaks and set the required symbol as expected.

INC-200936 · Issue 703345

SFTP support added to ValidateURL rule

Resolved in Pega Version 8.5.6

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

INC-202562 · Issue 701629

Updated FieldLevelAuditing logic for page comparison

Resolved in Pega Version 8.5.6

Optimistic locking was resulting in orphan assignments and the error "Error: Flow Not At Task, Error: Flow Removed". In addition, Get Next Work was causing duplicate Field Level Auditing records. This was traced to a missed use case in the logic used in pxFieldLevelAuditing where previousPage and PrimaryPage are compared to see whether they are equal or not, and has been resolved by adding one more condition to mark previousPage as null when the update date time or commit date time are not updated as part of processing.

INC-202943 · Issue 700195

WorkLink URL generation updated for security

Resolved in Pega Version 8.5.6

When using a WorkLink in an email, clicking the link and entering credentials on the login screen resulted in a 403 unauthorized error. This was due to a WorkLink URL generation issue caused by the non-encryption of the RedirectAndRun activity call in the URL, and has been resolved.

INC-204676 · Issue 699111

Localization added to subject line for SendEmailToAssigneeOnGoalTime

Resolved in Pega Version 8.5.6

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 706370

Check added to prevent duplicate approval by single agent

Resolved in Pega Version 8.5.6

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.

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