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-142589 · Issue 595489

Corrected tooltip evaluation for multiselect

Resolved in Pega Version 8.4.3

After adding help text for a multiselect help icon with overlay on hover field, the value was not being sourced. Changing to a different type of help text or control type worked as expected. This was due to an error in case sensitivity, using pyToolTip when it should have been pyTooltip, and has been corrected.

INC-142714 · Issue 596554

Recent Cases from different applications available to open

Resolved in Pega Version 8.4.3

An enhancement has been added which will allow opening other application assignments in the Recent Cases section of the current application when the user has access to multiple applications.

INC-143005 · Issue 596954

Fluid Overlay displays as expected in Firefox

Resolved in Pega Version 8.4.3

After upgrade, using the Overlay format "Fluid" to perform the screening matches task in CLM using Firefox had an overlay that covered the entire screen but was missing the scrollbar to manage the content. This has been resolved by adding changes to support dynamic content (with scrollbar) for center overlay.

SR-C68134 · Issue 423618

Support added for configuring key stores using prconfig or system properties

Resolved in Pega Version 8.1.3

Previously, stream service only supported key store and trust store configuration using Data-Admin-Keystore instances. Unlike cluster encryption, it did not allow the configuration of key stores using prconfig or system properties. In order to align Stream service SSL configuration with the rest of the platform, support has now been added for the following system and prconfig properties:-Dpega.cluster.keyStore -Dpega.cluster.keyStorePassword -Dpega.cluster.trustStore -Dpega.cluster.trustStorePassword

SR-D23239 · Issue 499591

Support added for multi-operator SAML logins

Resolved in Pega Version 8.4

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-D32655 · Issue 510345

Enhancement added to hold Change Tracker values until UI is loaded

Resolved in Pega Version 8.4

Sporadically, an agent attempting to answer a queued call within 10 seconds received a loading screen. By the time the load completed, the next agent had already taken the call. This is a scenario where based on a change, the agent was trying to refresh something on the UI (a section or harness) which was not yet loaded/present on the UI. To address this use case, an enhancement has been added to hold the change tracked values and handle them once the UI is loaded. The new function pega.ui.ChangeTracker.prototype.handlePendingCTChanges in pzpega_ui_changetracker.js is used to handle the pending CT changes. A hook has been added in the pzpega_ui_doc_lifecycle js file to invoke the above function once the UI is loaded.

SR-D18879 · Issue 500643

Logic update made to PrepareColors to resolve calculation ambiguity

Resolved in Pega Version 8.4

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 Rule-Utility-Function 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-D19299 · Issue 511324

Support added for calling Export to Excel directly from RD

Resolved in Pega Version 8.4

When using Export to Excel directly from a report definition, a date column specified using pxDatetime was shown as applied date format in the resulting Excel file. The column was formatted as expected if the export was called from an activity. This was traced to the recent refactoring of Export to Excel: it was not expected that it would be called directly, but rather that it would be invoked from a report viewer ruleform. In order to support this direct use, step calls have been added to the pzRDExportWrapper activity to call pzMergeAutoGen before the engine call. This step will merge the pyModes pages from pxDateTime control.

SR-D21527 · Issue 491739

Hidden filters will not be shown on the resulting report

Resolved in Pega Version 8.4

After setting up a Report Definition to be visible in report browser with all filters hidden, editing and saving the report resulted in the filter values being visible on the report. This has been resolved by modifying pzResolveCopyFilters activity so that If the filter view option is "Read only, allow no changes" and "Filter not visible in Viewer", it will skip copying the filter values on to the report definition page.

SR-D22319 · Issue 493660

Corrected Flex UI Alignment issues in Microsoft Internet Explorer 11

Resolved in Pega Version 8.4

In Microsoft Internet Explorer 11, a UI rendering issue was observed when Report Definition uses many columns. This was traced to Flex not being fully supported in Microsoft Internet Explorer 11, causing the flexResize function inside pzpega_ui_doc_lifecycle to not perform well when calculating harness width based on content. While there was a workaround of using the flag "pega.u.d.DISABLE_FLEX_RESIZE" to indicate the system should not execute that function, the issue has been resolved by setting table layout to auto.

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