INC-194180 · Issue 704639
MaxRecords increased to 9999 in GetChildCase report definition
Resolved in Pega Version 8.5.6
When more than 500 child cases were waiting for a single parent case to reach a status or to be resolved, only 500 cases were fetched by the report definition and the remaining cases were ignored. This has been resolved by updating the pyMaxRecords value for the maximum number of rows to retrieve to 9999 in the pzGetChildCases report definition.
INC-194429 · Issue 682881
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-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.