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.

SR-D19801 · Issue 495839

Corrected embedded section inside dynamic layout group becoming readonly

Resolved in Pega Version 8.2.3

When using a nested sections structure in a Dynamic Layout Group (tab), the fields inside the layout group were becoming readonly. This has been resolved by ensuring the controls present in second-level nesting onwards obey section read-only value in a dynamic layout group, and resolving the 'when' rule that governs the disabledwhen of link for all sections in a section include.

SR-D23164 · Issue 493796

Edit icon removed from deprecated custom skin styling

Resolved in Pega Version 8.2.3

Using custom styles as skin component is a deprecated feature as of Pega Platform v8.2. While existing styles will still be added to the CSS file when upgrading to or beyond this version, adding or updating custom skin styles is now handled through manual CSS files included in the skin. As part of this change, the edit icon for changing custom styles has been removed.

SR-D23239 · Issue 496707

Support added for multi-operator SAML logins

Resolved in Pega Version 8.2.3

When a SAML user logged in by Single Sign-On (SAML), the system processed the login to portal as a different operator if there was a function on the Attribute field under Operator identification in the SAML authentication service. In this scenario, using an expression for operator provisioning did not work because all SAML login sessions resolved to same first operator due to parseAndEvaluateExpression() in ExpressionHelper.java ignoring new expression arguments if the expression page already existed. To support the use of multiple operator logins in this format, the system has been updated to clone a new expression page for every session and update it with the correct expression arguments.

SR-D28034 · Issue 497838

Asynchprocessor generation code deprecated from distribution

Resolved in Pega Version 8.2.3

During a Pega Rules Upgrade of the environment, the error "duplicate key value violates unique constraint "pr_data_admin_pk" was observed. This exception originated from the "Upgrade Context" target while executing a query to fetch the missing ASYNCPROCESSOR requestors for all available system names, and was caused by the system attempting to insert a single ASYNCPROCESSOR requestor more that once in the shared layer. The need to generate missing requestors only applied for installations where a custom system name was provided to the deployment properties (setupDatabase), so by default the asyncprocessor generation code has been removed from the distribution as it is no longer required for upgrades. Default system behavior now is to use system-runtime-context in place of async requestors.

SR-D28293 · Issue 498234

Pega Survey answer values support special characters

Resolved in Pega Version 8.2.3

When using a Complex radio control (RadioButtonComplexQuestionSurvey), a selected option that used answer values containing special characters was cleared on refresh. This was traced to a mismatch between strAnswer and strValue in the control logic, and has been corrected.

SR-D28060 · Issue 498750

XSS filtering added to App Studio

Resolved in Pega Version 8.2.3

The pzDisplaySpaceFeedTitle control which is used to display the audit feed in Pega App Studio has been updated with XSS filtering.

SR-D26642 · Issue 499144

Layout Refresh on Value Change works with Property Empty

Resolved in Pega Version 8.2.3

Layout refresh on value change was working when changed from "Yes" -> "No" or "No" -> "Yes", but was not triggering the refresh when the first change was from Empty to "Yes" or "No". To resolve this, the pre-replacement event validationType attribute on this function has been removed so an empty value will be processed.

SR-D28869 · Issue 499316

Resolved Tooltip not relaunching after hide when using autocomplete controls

Resolved in Pega Version 8.2.3

When a tooltip was configured with SmartInfo and 'Auto-dismiss on hover away' was not checked, the tooltip disappeared when an autocomplete control was clicked and could not be reopened afterwards. The tooltip behaved as expected when it used input text control. This behavior was traced to autocomplete controls being set to hide all other active popovers because autocomplete results are displayed in a popover and only one active popover can exist on the DOM. However, it was seen that the tooltip's Smartinfo popover status was still active even though it was hidden, which is why it could not be launched again. To resolve this, when an autocomplete control is clicked, any active popovers being hidden will also be marked as inactive.

SR-D30272 · Issue 499439

Primary page paramter explictly set to resolve fix/edit Scheduled Tasks issue

Resolved in Pega Version 8.2.3

After upgrade, the top section of report details was getting blanked out when using the Reporting | Components | Scheduled Task to open a report and "update" it to fix issues. This was an unintended side effect of updating the Review harness to display the Perform harness when clicking Update, which was done to correct an earlier issue with UI validations when using the out of the box schedule report functionality. To resolve this, pxScheduleTaskWrapper has been updated to explicitly set the parameter page according to the primary page's values when not in the report browser.

SR-D29314 · Issue 499648

Support added for Authentication service rule attributes in embedded pages

Resolved in Pega Version 8.2.3

SSO login was not working, giving the error "Unable to process the SAML WebSSO request : No value specified for Attribute in SAML assertion". Investigation showed the Authentication service rule could only map attributes that are on the top level page and did not consider embedded page values. To resolve this, tools.getProperty will be used to fetch the property reference value instead of find Page and getString.

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