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.

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-D87188 · Issue 551349

Mentioned user in Pulse correctly converted to hyperlink

Resolved in Pega Version 8.3.3

In the Interaction portal, mentioning a user in Pulse using @ was not converting the name to the user name with hyperlink for Email Interactions. @ mentions were working as as expected in Phone Interactions. This problem was introduced as part of using OWASP to sanitize HTML user input in Rich Text support, and was due to OWASP converting @ to an HTML entity. To resolve this, the @ will be excepted from HTML conversion.

SR-D92688 · Issue 551339

Optional feature to improve pxETReport performance

Resolved in Pega Version 8.3.3

Poor performance was seen when using pxETReport. This was caused by the system loading the recent cases widget by looking up all the ET cases within last 30 days, opening each ET case to check if it is from the same pyFrom email address, and then if yes, opening its related service case. On a complex system, this was potentially a slow process. To improve performance, the "Related cases" feature can now be disabled through an overridable 'when' rule.

SR-D63638 · Issue 544015

Performance improvements for opening cases with embedded images

Resolved in Pega Version 8.3.3

Opening cases containing email interactions was taking an excessive amount of time. This was traced to the use of embedded images, icons, etc, in the message body and signature, and was caused by the pyGetAttachmentsbyCID activity running multiple times due to discussion threads that were duplicated over and over. In some cases, more than 360 calls to the database were seen. This has been resolved by shifting some case opening processes to executing when the listener thread gets the mail, and storing the results in a .pynote property, and a URL will be used to get images instead of embedding them directly to the HTML. If preferred, this can be reverted to the previous behavior by changing the when rule (pyUseCachedHtmlForDisplay) to false.

SR-D81707 · Issue 544671

Webchat bot interaction box cleared on submit

Resolved in Pega Version 8.3.3

After upgrade, when using Google Chrome responses to webchat bot questions were not getting cleared from the chat input window after the enter/send button was clicked. This has been resolved by changing the order of refresh section and set value and disabling submit on refresh when refreshing pzSubmitArea.

SR-D86837 · Issue 547992

Webchat interaction timeout updated

Resolved in Pega Version 8.3.3

Interaction timeout was not working as expected in Webchat channels. This was traced to the system looking for total interaction timeout instead of user inactive timeout, along with the Web chat interaction case clipboard page being stale. To resolve this, timestamp propagation has been updated for pxProcess in Work-Channel-Interaction.pxAcquireInteraction.

SR-D84364 · Issue 551399

Check for circular references added to SearchInventoryImpl to prevent recursive call

Resolved in Pega Version 8.3.3

An out of memory error was traced to SearchInventoryImpl infinitely recursing over a clipboard property, where the child property referenced a parent property and resulted in an endless loop. This has been resolved with the addition of a depth check to ensure that the search does not recurse infinitely.

SR-D77956 · Issue 547256

Column type configured correctly in Care Management

Resolved in Pega Version 8.3.3

When using database tables for concrete class groups with the column pyassignedoperator as character type without size, upon installation on higher environments the message "ERROR: length for type char cannot exceed 10485760 for colum "pyassignedoperator" CHAR (2147483647)" appeared. As a workaround it was possible to manually change the column type, but this issue has been resolved by updating the handling of BPCHAR types while cloning the table. BPCHAR type will be taken as CHAR.

SR-D85745 · Issue 545904

DASS and DAS associated to the Pega-ProcessCommander Ruleset

Resolved in Pega Version 8.3.3

An upgrade was failing at the point of Pega Rules Upgrade in the Installer Instance with the error "Encountered database exception when preprocessing deferred operations <insert updatesCache instance DATA-ADMIN-SYSTEM PEGA not only if new>. This node not found in the database - Either the record was never saved or was deleted. Unable to join the cluster." This error occurred because the strategic application import during upgrade manually included a "systemname" DASS instance which had a value other than "prpc". This caused a override of the platform shipped DASS (with value "prpc), which is required by the upgrade. In order to avoid this condition, DASS and DAS have been associated to the Pega-ProcessCommander Ruleset.

SR-D81572 · Issue 551026

JDBC URL handling added for Oracle over TCPS

Resolved in Pega Version 8.3.3

While attempting to upgrade an environment over TCPS, the script was failing. The same environment ran without issue on Tomcat with the same URL. Investigation showed the JDBC url was not correctly generated while running the upgrade: in a standard scenario, there will be no spaces in the JDBC URL specified. However, because Oracle can send spaces as part of JDBC URL and cause this issue, an update has been made which will quote the JDBC URL argument for the ant target in setupDDL.xml.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us