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-D78045 · Issue 539890

Cleanup added for staging directory

Resolved in Pega Version 8.3.2

Temporary files from imports and exports (from DevOps) were filling up the staging area disk space because there was no automatic process for cleaning up these local files. This has been resolved by adding an enhancement that will clear the directory on Engine Startup and any time ParUtils.setStagingDirectory gets called to initialize the staging directory.

SR-D83053 · Issue 544267

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

Resolved in Pega Version 8.3.2

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-D15231 · Issue 484813

Resolved Java code compilation issue due to localized field value

Resolved in Pega Version 8.3.2

After installing the French language pack, a java compilation error occurred due to the dynamic parameters being localized, causing a mismatch for the field values. For example, the Field value pyFactory was translated from "com.pega.dsm.dnode.impl.dataset.cassandra.CassandraDataSetFactory" to "Ensemble de données Usine com.pega.dsm.dnode.impl.dataset.cassandra.Cassandra" in all Data-Admin classes and was being interpreted in the generated java. This has been corrected.

SR-D32528 · Issue 502216

Reduced triggering for checkbox click calling resize

Resolved in Pega Version 8.3.2

When using Microsoft Internet Explorer, checkboxes were slow to respond. For example, when clicking two checkboxes in succession, the second checkbox did not change. This was traced to the Layout Resize function getting called numerous times by the _toDisableSlideOnTabsClick and _resizeActions functions during onload refresh. This has been resolved by updating the system so that an LG header cell item checkbox click will not trigger the resize.

SR-D35956 · Issue 521641

Handling enhanced for invalid date values in date/time

Resolved in Pega Version 8.3.2

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-D37348 · Issue 514838

Added handling for placeholder in Multi-Select List Control

Resolved in Pega Version 8.3.2

After adding a placeholder in Multi-Select dropdown properties to hold the default value as 'please specify' by way of a refresh section on the action tab of multi-select property, the multi-select drop was showing the 'please specify' placeholder after refreshing the section even though there was value in it. This has been resolved by adding handling to make the placeholder empty when there are values.

SR-D40778 · Issue 512974

Asterisk symbol displayed for radio button set to required always

Resolved in Pega Version 8.3.2

When marked as required, the "Asterisk" symbol did not show up on the radio button label. This was traced to an XML cleanup issue with the pyReqRunOnClient property when required was configured as 'always' and has been corrected.

SR-D40803 · Issue 511591

JSON parsing error on export resolved by ensuring parameter encoding

Resolved in Pega Version 8.3.2

Menu items like "PDF" and "Excel" were not loading on click of the "Export" Button, and an "Exception in parsing JSON" message was logged. The export worked as expected when the menu rule actions of each menu item were modified to remove the openurlinwindow actions. This was traced to the Response JSON being broken due to a invalid format created when the "propositionName" was passed as an unencoded parameter when the report was exported. This has been resolved by ensuring the input parameters are encoded before creating the URL.

SR-D40938 · Issue 509684

Free form layout controls will be converted to dynamic layout

Resolved in Pega Version 8.3.2

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-D40941 · Issue 512591

Identifier property added for worklist with filter by format

Resolved in Pega Version 8.3.2

After configuring a Grid layout which displayed a users worklist, one of the properties representing the column in Grid had the property type as boolean. The property was derived from another report definition in the main report and a join was performed to display the property. Investigation showed that the filter for Boolean column did not show any filter values like ( [No Value, Y,N ) when run through a case Manager Portal, however the Boolean Column filter worked when run through Report Definition. Other properties from the same class that were not boolean worked with the filter. This was traced to the WorkListWidgetGridsAuto being set to Optimize code, causing filter by format to not be visible in the column properties of pxPages. To resolve this, code has been added for the identifier property

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