SR-D76415 · Issue 540319
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-D77004 · Issue 542347
View Full History will not include private edits
Resolved in Pega Version 8.3.2
After upgrade, clicking 'View Full History' and then 'History of All Versions', showed the history of discarded private edits of other users. This was an inadvertent side effect of work done to improve the support for rollback and migration, and has been resolved by updating the system to not save the history when in a personal ruleset (checkouts/private edits). The help documentation has also been updated to note there is no history available for checkouts/private edits.
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-D79178 · Issue 543310
SameSite cookie setting added for Mashup support in Google Chrome v80+
Resolved in Pega Version 8.3.3
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; this value automatically includes the “secure” cookie flag, which enforces HTTPS for the Pega server and mashup. For mashups to work, SameSite should be set as None. Create a Dynamic system setting in the Pega-Engine RuleSet with the name “security/csrf/samesitecookieattributevalue” and the value "None" and restart the server. (The SameSite value "None" works only in secure HTTPS connections.)Note: The SameSite cookie may be set to None/Lax/Strict, based on the requirement. For cookie requirements other than mashup, it should be set as either Strict or Lax, depending upon your application.
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.