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.

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.

SR-D26505 · Issue 499664

Check added to isConnectorProblemFlow for empty newAssignPage

Resolved in Pega Version 8.2.3

When the isConnectorProblemFlow 'when' rule had a "newAssignPage.pyErrorStep = .pxFlow(newAssignPage.pyFlowInError).pyLastFlowStep" condition and was triggered on click of an actions button in the review harness, an error appeared. This was traced to newAssignPage being an empty page group property reference, and the issue has been resolved by adding a check to isConnectorProblemFlow for the existence of newAssignPage before referring to a property in it.

SR-D23906 · Issue 499988

Case status correctly updated when using RDA

Resolved in Pega Version 8.2.3

When a Assignment was routed to a work queue and Flow Action post processing was set to trigger an RDA Automation to update some case property, an error appeared saying there was no data available on the Page and the case status was not updated when it moved to the next stage. This was an issue with case status not being correctly updated when using robotic automation, and has been resolved.

SR-D29416 · Issue 500133

Email template content editors visible when using Smart Investigate

Resolved in Pega Version 8.2.3

When specialized email correspondence templates were used with the Smart Investigate Framework, the correspondence rules did not have all the default values used in visibility conditions. This caused the 'when' rules pzShowSourceOnlyEmailEditor and pzShowBasicEmailEditor to evaluate to false and not display the source stream. To resolve this, UpgradeOnOpen has been added for correspondence rules to set the value for the visibility of rich text editor for source code viewer in order to support the use of custom templates with Smart Investigate Framework.

SR-D18879 · Issue 500641

Logic update made to PrepareColors to resolve calculation ambiguity

Resolved in Pega Version 8.2.3

When a Report Definition was summarized, the executed report showed a graph for multiple categories but generated the error "No data to display" if given a single category. This was traced to an ambiguity in the Java syntax of the RUF pzPrepareColors that led to a NegativeArraySizeException on a customer's environment. To resolve this, parentheses have been placed around a ternary operator to ensure the correct order of operations.

SR-D32222 · Issue 500899

Auto-generated controls with images supported in export to Excel

Resolved in Pega Version 8.2.3

When attempting to display a column as an image, changing the column format to "pxCheckbox" showed an image while running the report if the value was true, but blank values were displayed when the report was exported to Excel. Investigation showed that the value was being returned as null when a boolean value was set on a column and the option for the auto control was set to show as an image due to the formatted value being returned as an HTML element instead of a boolean value. To correct this, AutoGenReportUIField has been modified so that auto-generated controls that are shown as images are converted to text upon export to Excel.

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