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-D32991 · Issue 504130

Email Discussion Thread retains Formatting

Resolved in Pega Version 8.2.4

CSS styles were not being retained in the discussion thread when replying to InboundCorrespondence cases. This was traced to a missing value in Param.latestReply activity pzCreateExternalPostFromMail, and has been resolved by setting an initial plain text value to the param.latestReply before it is set with the HTML value. This prevents having a blank parameter value if the incoming HTML value is empty.

SR-D37757 · Issue 507967

Pulse delete icon repaired

Resolved in Pega Version 8.2.4

After upgrade, it was no longer possible to delete one's own comment in Pulse. This was traced to the section pzDeleteMessage having two dynamic layouts with icon as image configured. During runtime, this section was present in the DOM yet the icons were not visible when the conditions configured were returned as true. This was caused by an error in the generated java for the layout, and has been corrected.

SR-D18853 · Issue 503275

Visibility on client check removed to enable Pulse on click

Resolved in Pega Version 8.2.4

When Pulse was configured on click of a icon, the comment section was not visible. Investigation showed that at the time of DOM load, pyMessage property was not available in the DOM because 'Run visibility condition on client' was checked by default. Visibility on client checks have been removed to resolve this issue.

SR-D33491 · Issue 511727

Code fragment removed to resolve CookieDisabledException

Resolved in Pega Version 8.2.4

After upgrade, a CookieDisabledException occurred after a post activity was invoked in the single sign-on (SSO) authentication service. This was traced to the site using the deprecated flag "redirectguests" as part of SSO-based login for mashup usecases. This flag was used to check if a cookiedisabled exception was thrown or not, and if there was no cookie, if a requestor was authenticated in first request. However, the flag has been removed as part of work done to omit the Cookie support check on Mobile App UAs. Code that supported the use of this flag remained after that work and led to the exception being generated, but has now been removed as well.

SR-D43811 · Issue 511921

Code fragment removed to resolve CookieDisabledException

Resolved in Pega Version 8.2.4

After upgrade, a CookieDisabledException occurred after a post activity was invoked in the single sign-on (SSO) authentication service. This was traced to the site using the deprecated flag "redirectguests" as part of SSO-based login for mashup usecases. This flag was used to check if a cookiedisabled exception was thrown or not, and if there was no cookie, if a requestor was authenticated in first request. However, the flag has been removed as part of work done to omit the Cookie support check on Mobile App UAs. Code that supported the use of this flag remained after that work and led to the exception being generated, but has now been removed as well.

SR-D32991 · Issue 504129

Email Discussion Thread retains Formatting

Resolved in Pega Version 8.3.1

CSS styles were not being retained in the discussion thread when replying to InboundCorrespondence cases. This was traced to a missing value in Param.latestReply activity pzCreateExternalPostFromMail, and has been resolved by setting an initial plain text value to the param.latestReply before it is set with the HTML value. This prevents having a blank parameter value if the incoming HTML value is empty.

SR-D28342 · Issue 504970

ChatMashup loading issue with IDP resolved

Resolved in Pega Version 8.3.1

When using a harness containing chat scripts via Mashup that called an activity to set parameters, attempting to launch the Mashup from an external application failed on the first attempt: an incorrect URL was generated and the activity was not triggered, resulting in an empty harness. The second attempt to launch the Mashup worked as expected. This was seen when using an IDP initiated Login with query string - pyActivity= classname.ActivityName, and there was a workaround to use SP initiated login or to use the activity URL directly on the IDP portal. Investigation showed that the resourcePath was coming as http in SSL enabled system, but the reqURI was still https. To correct this, the system has been updated so that if the reqContextURI starts with https and the requestURL starts with http, then the requestURL will be converted to https.

SR-D28060 · Issue 498749

Cross-site scripting filtering added to App Studio

Resolved in Pega Version 8.3.1

The pzDisplaySpaceFeedTitle control which is used to display the audit feed in Pega App Studio has been updated with cross-site scripting filtering.

SR-D28293 · Issue 498233

Pega Survey answer values support special characters

Resolved in Pega Version 8.3.1

When using a Complex radio control (RadioButtonComplexQuestionSurvey), a selected option that used answer values containing special characters was cleared on refresh. This was traced to a mismatch between strAnswer and strValue in the control logic, and has been corrected.

SR-D30428 · Issue 503424

Added handling for deprecated UI Kit in Pulse OpenURLInWindow

Resolved in Pega Version 8.3.1

After upgrade, clicking on a link in a Pulse comment opened a new window with an error message indicating no content was returned. Investigation showed that if an older deprecated version of the UI kit was used, 'Open URL in window' was configured as Run Script function. The more recent versions use an OpenURLInWindow action. To resolve this, the script has been updated to use an action and pass the correct parameters.

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