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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-D78987 · Issue 544061

Support for custom jvm.args added

Resolved in Pega Version 8.2.6

In order to support Oracle PKI and other ticket based authentication, support has been added for custom jvm.args properties to setupDatabase and prpcUtils properties files.

SR-D79178 · Issue 543312

SameSite cookie setting added for Mashup support in Google Chrome v80+

Resolved in Pega Version 8.2.6

The Google Chrome browser version 80 and above now treats SameSite with a blank value as "Lax" by default, causing mashup scenarios to break. In order to compensate for this change, support has been added for setting SameSite=None in Cookie Settings in the CSRF LP (DevStudio-> System-> Setting-> CrossSiteRequestForgery) which will enforce HTTPS for the Pega server and mashup. Note: The SameSite cookie may be set to None/Lax/Strict, based on the requirement. For mashups to work, SameSite should be set as None. To follow proper security standards, it should be set as Strict.

SR-D83053 · Issue 544268

SameSite cookie setting added for Mashup support in Google Chrome v80+

Resolved in Pega Version 8.2.6

The Google Chrome browser version 80 and above now treats SameSite with a blank value as "Lax" by default, causing mashup scenarios to break. In order to compensate for this change, support has been added for setting SameSite=None in Cookie Settings in the CSRF LP (DevStudio-> System-> Setting-> CrossSiteRequestForgery) which will enforce HTTPS for the Pega server and mashup. Note: The SameSite cookie may be set to None/Lax/Strict, based on the requirement. For mashups to work, SameSite should be set as None. To follow proper security standards, it should be set as Strict.

SR-D83192 · Issue 545057

JobScheduler DST handling updated

Resolved in Pega Version 8.2.6

When the locale being used changed out of Daylight Savings Time, scheduled jobs did run at the same local time as before but instead ran an hour earlier than expected. Investigation showed that jobscheduler calculated the next runtime based on the time difference from the cluster reference time and current time in milliseconds, and this offset in milliseconds was added to next run time. Since the cluster was started in DST, the job was running on same time due to the time difference. To resolve this, the system will use a calculation offset and set hours/minutes to nextRunTime object so that calendar lib handles daylight savings.

SR-D34359 · Issue 510600

StretchTabsWidth performance improvements

Resolved in Pega Version 8.2.6

Slowness was seen when a new intent task was created through an interaction. To improve performance, some of the unnecessary calls to the Layout Group _updateStretchTabsWidth() function have been eliminated, and the function code has been updated to use native javascript performant helper functions so it starts rendering sooner. A flag has also been added to disable addnewtab and resizeactions: these need to be enabled through pega.u.d.DISABLE_LG_RESIZE and pega.u.d.DISABLE_ADDNEWTAB.

SR-D35956 · Issue 521642

Handling enhanced for invalid date values in date/time

Resolved in Pega Version 8.2.6

Refreshing a section or entering an invalid date was causing the date/time to be reset to the current date. This has been resolved by modifying the logic and adding conditional checks in 'pzpega_ui_formatDateTime.js'.

SR-D39356 · Issue 515148

StretchTabsWidth performance improvements

Resolved in Pega Version 8.2.6

Slowness was seen when a new intent task was created through an interaction. To improve performance, some of the unnecessary calls to the Layout Group _updateStretchTabsWidth() function have been eliminated, and the function code has been updated to use native javascript performant helper functions so it starts rendering sooner. A flag has also been added to disable addnewtab and resizeactions: these need to be enabled through pega.u.d.DISABLE_LG_RESIZE and pega.u.d.DISABLE_ADDNEWTAB.

SR-D40938 · Issue 509685

Free form layout controls will be converted to dynamic layout

Resolved in Pega Version 8.2.6

After upgrade, a a pzActionDropdown control that was inside a pyActionDropdownSection was not visible anymore. Using the pzActionDropdown control directly worked as expected. Investigation showed that pyActionDropdownSection was using Freeform layout instead of the upgraded Dynamic Layout, and that the custom control was failing to generate the markup whenever drag/copy-paste was used for the control in any layout. To resolve this, the system has been updated so it will remove the control from a free form layout and use dynamic layout instead.

SR-D44943 · Issue 527920

Handling added for mousdown triggers in Firefox dropdown and sutocomplete controls

Resolved in Pega Version 8.2.6

After recording a test case that includes entering data into an autocomplete, the data was not actually entered into the autocomplete when the test was executed but the test step was marked as successfully executed. Other tests for other similar autocompletes appeared to execute as expected. This was due to a mismatch between the sequences of events that are fired in the Google Chrome and Firefox browsers: the system is listening for a mousedown event to record a new step, but the browser-specific behavior is different. Google Chrome: mousedown focus click change Firefox: mousedown focus mousedown change As this difference in events order is browser behavior, code has been added that will handle the specific Firefox case where mousedown triggers on invalid target elements related to dropdown and autocomplete controls.

SR-D45101 · Issue 512528

Added support for Helper Text Question Mark with visibility condition

Resolved in Pega Version 8.2.6

The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file.

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