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-D33445 · Issue 505994

Handling added for context switching with Ajax container in Timeline

Resolved in Pega Version 8.2.4

When using Interaction Portal -> Overview -> Timeline and opening a case that uses an AjaxContainer, clicking on an icon in the Timeline without having first clicked anywhere in the document was generating an exception. If there was a click in the document body first, clicking on the icon worked as expected. This has been resolved by adding a parameter to registerContextSwitching method to handle customeDOMEvents along with a condition to check if pega.u.d.isAjaxContinerExists is a function, which will register the Context if 'true'.

INC-169116 · Issue 654256

Correct time zone chosen for fr_Fr appointment functionq

Resolved in Pega Version 8.7

When using the "fr_Fr" location and and "Europe/Paris" time zone for appointments, a null pointer exception was seen related to the function getStartOrEndDateTime. Investigation showed that the incorrect time zone was being picked from the fr_FR.xml file when parsing the date. To resolve this, 4 letter time zone codes have been moved above the 3 letter time zone codes.

INC-163544 · Issue 639301

Accessibility corrected for Cosmos user portal left navigation panel

Resolved in Pega Version 8.7

It was not possible to see the focused control label in the left pane of the Cosmos user portal because it was not expanding when its control received focus from tabbing. Investigation showed the class acting as a polyfill for :focus-within was applied only on the observed element when using Microsoft Explorer 11, and this has been resolved by updating the CSS selectors and ensuring the class is applied to every parent element down the DOM tree.

INC-183712 · Issue 674132

IndexOf updated to remove extra bracket

Resolved in Pega Version 8.7

When trying to open a section rule, content was not loading if values were derived using a report with column containing a function. This occurred when the section rule included a table referencing the report where one of the section table cells had its Property value set to the function. To resolve this, indexof has been updated to not include closing > as the HTML returned from the server now includes an attribute on that tag.

SR-B41316 · Issue 306255

Resolved missed cases in the WO case tree

Resolved in Pega Version 7.3.1

Sometimes several cases were missed in the case tree, shown in the right side of an opened WO. Access was not available for the corresponding WO and assignments. The root cause was a WHEN condition in WORK-COVER- PZLOADNESTEDCASESFORCLASS property "local.ProcessedItemKeys" containing numbers of processed WOs separated by a space, for example, "KPI-101 KPI-72 KPI-52". The WHEN condition checks for presence using "contains", leading "KPI-10" to be ignored and not displayed in cases where "KPI-101" already presented. To correct this, the system will consider the delimiter "\t" while checking the WHEN condition.

SR-B41316 · Issue 306260

Resolved missed cases in the WO case tree

Resolved in Pega Version 7.3.1

Sometimes several cases were missed in the case tree, shown in the right side of an opened WO. Access was not available for the corresponding WO and assignments. The root cause was a WHEN condition in WORK-COVER- PZLOADNESTEDCASESFORCLASS property "local.ProcessedItemKeys" containing numbers of processed WOs separated by a space, for example, "KPI-101 KPI-72 KPI-52". The WHEN condition checks for presence using "contains", leading "KPI-10" to be ignored and not displayed in cases where "KPI-101" already presented. To correct this, the system will consider the delimiter "\t" while checking the WHEN condition.

SR-B56485 · Issue 312961

Mashup gadget cookie requests consolidated in Safari

Resolved in Pega Version 7.3.1

In order to resolve an issue when using Safari where Pega was displaying a message to allow cookies for every Mashup gadget, the isCookieConsentRequired method in PegaCompositeGadgetMgr.js has been updated to check if the host URL and gadget URL are the same to avoid duplicate messages.

SR-B43999 · Issue 310047

Corrected accessibility for complex dynamic layout headers

Resolved in Pega Version 7.3.1

JAWS was not able to interact with complex nested dynamic layout structure when the innermost dynamic layout had a Header / "Title" set. This was traced to the generation of empty tables in the Dynamic layouts related to the use of the Show container Icons checkbox, and has been fixed.

INC-194269 · Issue 681046

Added handling for Create Source and Target properties of Date

Resolved in Pega Version 8.7

A report definition was not displaying results after update, and a stack overflow was reported. This was a missed use case for Create Source and Target properties of Date, and has been resolved by adding a boolean flag to avoid autochain during validations when data type is Date.

INC-186138 · Issue 668811

Charts sourced from Report Definition show correct color post-update

Resolved in Pega Version 8.7

After update, the color coding was not working on charts sourced from a report definition. This was due to the correct seriesType not being determined when function aliases were used in charts, and has been resolved by adding a condition in configuration.java to determine correct the SeriesType.

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