SR-D90485 · Issue 549270
SameSite cookie setting added for Mashup support in Google Chrome v80+
Resolved in Pega Version 8.4.1
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-D90524 · Issue 549048
SameSite cookie setting added for Mashup support in Google Chrome v80+
Resolved in Pega Version 8.4.1
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-D68311 · Issue 535988
Corrected table row highlighting on iPad
Resolved in Pega Version 8.4.1
A table row was highlighted when clicked on an iPad in landscape view, but when the device was rotated to portrait view the row was not highlighted. This was traced to the background CSS overriding the selected style, and has been corrected by modifying py-responsive-overrides.css.
SR-D74704 · Issue 535943
Section and navigation rule localization added
Resolved in Pega Version 8.4.1
Localization has been added for sections and navigation rules that include some of the out-of-the-box rules like Locked and Get help.
SR-D76178 · Issue 538602
Corrected Cosmos dropdown positioning in right-to-left locales
Resolved in Pega Version 8.4.1
When using the Arabic locale with the Cosmos UI, the dropdown was located on the right side of the field instead of the left side. This has been corrected.
SR-D36319 · Issue 507362
Pulse mention emails correctly sent for Japanese locale
Resolved in Pega Version 8.4.1
When an operator with Japanese locale (ja_JP) was mentioned in a Pulse comment, email notifications were not being sent. This was working as expected for other operators in different locales. Tracing the pyProcessNotification Queue Processor revealed issues with the pySendNotification context that caused D_pyPulsePostDetails to not load. This has been corrected with modifications to the correspondence rule pyAddUserMentionedPost in the PegaSocial_ja 08-01-01 ruleset.
SR-D44769 · Issue 531441
Resolved non-template harness stale reference for navigation menu
Resolved in Pega Version 8.4.1
Post upgrade, the navigation menu was initially present but disappeared on click of a menu item. This issue was seen only when the harness was non-template and SPA was enabled on the dynamic container: when launch harness was done on the same harness, change tracker created a new thread object but the client cache was holding the stale reference. When using template harness, mergeBigData adds all the new details into the stale object, preventing this issue. To resolve this issue for non-template harnesses, initChangeTracker in pzpega_ui_doc_lifecycle file has been updated.
SR-D57629 · Issue 536628
Navigation sub menu shows all options
Resolved in Pega Version 8.4.1
The switch app menu was running off the bottom of the screen, and using arrow keys to navigate it caused the whole portal to jump up. This was traced to the sub-menu style attribute 'top' being changed to '0' if it was given a negative value. To resolve this, a condition was added to check whether the rendering sub-menu height is greater than viewport, and adjust the top attribute value accordingly.
SR-D58868 · Issue 531801
Check added for unicode calendar values
Resolved in Pega Version 8.4.1
After creating a repeating grid section for work report definition with enabled filter option, running the section and giving the filter value in unicode calendar form such as ２０１９／１１／１２ did not pass validation. This has been resolved by adding a check for unicode values.
SR-D61560 · Issue 539475
Support added for multiselect control with SmartTip for iPad
Resolved in Pega Version 8.4.1
When using a multiselect list control to a lproperty with Smart Tip configured, choosing one item on an iPad and then trying to tap or drag down the vertical scrollbar caused all listed items to disappear. To resolve this, the multiselect control has been updated to handle the popover exit on smart popover hover along with arrow key navigation support for tablets.