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-192500 · Issue 684336

ManageRecentContent tab icons updated for accessibility

Resolved in Pega Version 8.5.6

The PegaSocial-Document "Manage Content" flow action (Work-.pzManageRecentContent) shows a tabbed layout with images and labels for "Rich Text", "Local File", "Add Existing" and "URL". These are displayed via the pyEnterCaseDetails section rule. In order to meet accessibility standards, the underlying PNG files (pyreferexistingdocument.png, pyaddurl.png, pyrichtextdocument.png, pyuploadadddocument.png) have been updated to meet the necessary 3:1 contrast ratios.

INC-192673 · Issue 689553

Tab highlighting updated

Resolved in Pega Version 8.5.6

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

INC-193071 · Issue 686647

Find by ID functionality repaired

Resolved in Pega Version 8.5.6

After update, the Find by ID Functionality was not working as expected. This was an unintended side effect of work done around the inheritance of default values when the portal pyPortal.pyDesktopType was set to Composite, and has been resolved by modifying the previous work to move the check to verify if the pxCurrentWorkPool== "" to a later step.

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.

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