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-163596 · Issue 636235

Checkboxes receive correct focus with accessibility

Resolved in Pega Version 8.6

It was necessary to click the tab twice in order to check the checkbox in the filter popup. This has been corrected by adding a check in the firstfocuselement method so the focus is placed correctly over input type elements.

INC-163651 · Issue 636900

Cancel button in offline works as expected

Resolved in Pega Version 8.6

When using the mobile app offline, clicking 'cancel' after creating a new case did not remove the case, but instead returned to the review screen. This was traced to the logic used to evaluate the conditions, and has been resolved so that the 'cancel' button will return to the worklist if offline, or display save/delete options when in the create stage of the online app.

INC-164311 · Issue 635785

Correct datetime target property used

Resolved in Pega Version 8.6

When using a declare expression for a datetime property to get its value from another datetime property, attempting to change the source datetime later resulted in the error "28-mar-2021 is not a valid date/time value". This occurred when the source datetime property had display readonly formatting, and was traced to the formatted value being sent in the callGetTargets API instead of the selected date value, which caused the function to be returned as empty because there was no target property in the same page before submission. To correct this, a check has been added which will get the value from data-value instead of element.value and will skip callGettragets if the target is empty.

INC-169907 · Issue 648484

Handling added for element outside viewport in overlay

Resolved in Pega Version 8.6

The left attribute from overlay styles was changing from "0" to a negative value (dynamically depending on screen size) while scrolling the results up and down. This caused issues such as attempting to view the duplicate case analysis screen or having the tool tip move to the extreme left when hovering the mouse on a link and scrolling. This was traced to an overlay launched from a table: if client.left was zero, the overlay left was given a negative value which causes the overlay to be shifted towards left side of the screen. To resolve this, an extra condition has been added to check if the associated element is outside the viewport when an overlay is launched from a table, and if so apply a flippedX value for left property.

SR-69015 · Issue 619995

Unescaping characters implemented for expressions

Resolved in Pega Version 8.3.6, Resolved in Pega Version 8.4.4, Resolved in Pega Version 8.5.3, Resolved in Pega Version 8.6

An issue where expression builder statements were evaluated differently at runtime than at testing has been resolved. Pega Platform expressions with String literals(that is, sequences of characters enclosed in quotation marks) now unescape characters in strategy shapes such as Set Property or Filter.

SR-C49664 · Issue 435310

Updates made for usage validation utility Run report checkbox and buttons

Resolved in Pega Version 8.1.5

The 'Review mode only' checkbox wasn't working for any browser, and the 'Run Report' button wasn't working in IE. This has been resolved by updating the javascript used to invoke the Run Report button to be better integrated with IE, and by adding additional handling to set the ID for the checkbox.

SR-C74677 · Issue 418339

ADM pulse timing changed to inprove performance on very large clusters

Resolved in Pega Version 8.1.5

ADM uses a pulse that checks if any models need to be updated. This uses a Cassandra query which has no "where" clause, causing poor performance for very large clusters. For immediate relief of this issue, the pulse configuration has been updated to increase the timing from 30 to 300 seconds so it fires less often. Model updates typically happen every x hours and often the pulse will not detect any models that would need to be updated. Further improvements in this process will be available in a future release.

SR-C77730 · Issue 437101

Resolved case lock release improved

Resolved in Pega Version 8.1.5

Cases created through the create work object were unnecessarily holding onto locks for up to two hours. This was traced to a defer-write scenario for mobile devices which did not return the correct status needed for "no further assignments". In order to resolve this issue, a new parameter "returnNextActionInfo" of type boolean has been added to svcPerformFlowAction. This parameter will be always set as false when calling this activity from sync up so all locks will be closed and released.

SR-C80622 · Issue 424876

GenerateContainer updated to prefer icon given in skin over hardcoded icons

Resolved in Pega Version 8.1.5

When trying to change the Expand/Collapse icon for dynamic layout by defining a custom format in the app skin, changes made in the Expand icon image and Collapse icon image were not reflected. This was due to the CSS selector being overriden with a hardcoded arrow icon instead of automatically taking the icon from the skin rule. To resolve this, the selector and conditions used in GenerateContainer.java have been modified such that the icon added in the skin should be picked automatically instead of any hardcoded icon available.

SR-C81185 · Issue 427995

Accessibility enabled Layout group tabs browsing corrected

Resolved in Pega Version 8.1.5

When using Layout group (Tab) or a Tabbed Layout for viewing client information in Tabs with Accessibility enabled, the system was reading each tab and its content but then focus was returning to the browser and tracing through all elements before moving on to the next tab. This was traced to an incorrect tabindex setting in the pzpega_ui_template_layout_header file, and has been fixed.

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