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-185847 · Issue 669526

Handling added for disabling weekends when no weekends are available

Resolved in Pega Version 8.7

A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.

SR-122409 · Issue 182081

Refresh when active' tabs no longer affecting other tabs

Resolved in Pega Version 7.1.8

A tab using the 'Refresh when active' setting, could cause the content of other non auto refreshing tabs to re-execute. E.g. Report Definitions that are sourcing repeat grids in other tabs. This occurred when using the 'Refresh when active' setting on a tab whose content is a Dynamic Layout (the out-of-the-box default when adding a tab) with an embedded section. There was a local workaround of updating tabs to use the required section as the top level content rather than using a dynamic layout with an embedded section, and this has now been incorporated into the software. The refresh when active setting is still available in this configuration.

SR-127491 · Issue 193606

Resolved runtime error when editing complex grid cells

Resolved in Pega Version 7.1.8

When using grid edit mode inline on a grid with a section inside a cell that includes a checkbox and a 'when' condition, a runtime error appeared when the cell was clicked. This was an issue with the wrong reloadElement being passed in the editRow() API, and this has been corrected.

INC-173162 · Issue 650795

Certificate match will use Subject Distinguished Name

Resolved in Pega Version 8.7

Signature verification was failing due to the system not finding the matching root certificate for the chain. The root certificate was in the trust store, but the system found a different certificate first and that other certificate (an intermediate certificate) was not considered a valid certificate for validating the whole certificate chain. This was traced to filtering on the Issuer Distinguished Name (DN) instead of the Subject DN and was due to intermediate certificates potentially having the same Issuer as a root certificate (e.g. if that root certificate was used to create the intermediate certificate). To resolve this, an update has been made to check the Subject DN instead of Issuer DN.

INC-189047 · Issue 674759

Session timeout adjusted for use with Apple Safari

Resolved in Pega Version 8.7

A configured browser session logout timer was not working with the Apple Safari browser. This was traced to browser-specific handling for self.location.href and has been resolved by adjusting the logic and moving it inside a setTimeout to improve cross-browser compatibility.

SR-125590 · Issue 189717

Refresh context retained when switching tabs in repeating layouts

Resolved in Pega Version 7.1.8

When a repeating tabbed layout is configured to include "Refresh other section" functionality to refresh sections within the tab, it worked correctly when the operator created a new tab and performed all the work in that tab. However, if the operator switched to another tab and then returned to the original tab, the refresh other section and any associated activity used the context of the previously opened tab and it appears to the operator as if the action they have just performed has not worked. This was caused by the Refresh Other section not supporting multiple section refresh if the section is in a repeating layout (i.e. the same named section appears multiple times, once in each tab). The system has been updated to refresh ALL the occurrences of the same section in UI to resolve this issue.

INC-175892 · Issue 651962

Updated logic for Spinner API used in DateTime control

Resolved in Pega Version 8.7

When selecting 11, 22, 33, 44 in minutes in the DateTime picker, 11 was rounded off to 10, 22 was rounded off to 20, 33 was rounded off to 30, etc. This was due to the match and increment behavior in the UI Spinner Js API used by the DateTime control, and has been resolved by modifying the logic used to calculate the nextIndex in the keydownHandler API under ui_spinner.js .

SR-116764 · Issue 199322

modal dialog retains fixed size when traversing a flow

Resolved in Pega Version 7.1.8

When a modal is configured to have different formats, those formats were missing upon going to the next assignment. This was caused by the format of the modal being reset Configured Modal Format was not being applied once we process flow in modal dialog. This has been fixed by passing the modalStyle parameter to the modal dialog callback.

INC-174625 · Issue 655242

Admin Studio will consider cluster protocol when returning listener status

Resolved in Pega Version 8.7

When using a few nodes in standalone mode for BIX extract combined with server nodes using Hazelcast, opening the admin studio pages with service discovery caused an error to be thrown. This was traced to the system writing an entry to pr_sys_statusnodes table as an embedded node whenever a BIX extract was triggered, causing those standalone nodes to be incorrectly considered by the listener landing page. This has been resolved by configuring the system to either return the local member when the cluster protocol is standalone or to return all Hazelcast members if the cluster protocol is Hazelcast.

SR-128684 · Issue 194308

Corrected save-as for Activity using API "02"

Resolved in Pega Version 7.1.8

In drop down generation, if a value was empty then adding the selected attribute for the first option assuming no options should have the empty value other than no selection text. To make this work as expected, if the value is empty then the system will add the selected attribute on the option which has empty value to avoid setting first option value to the hidden field.

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