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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A8445 · Issue 220085

Ensured display of empty user worklist section in hybrid client

Resolved in Pega Version 7.2

The user worklist section was not being displayed in the hybrid client if the login had no assignments (the WL(D_pyUserWorkList pxresultcount is zero) and the crewleaderworklist harness had a repeating dynamic layout. This has been corrected.

SR-A8217 · Issue 223611

Added server retry for push notifications in Sales Automation 7.14 / SFADevelopment for Android

Resolved in Pega Version 7.2

Push Notifications were not working on Sales Automation 7.14 / SFADevelopment for Android. This was traced to an error returned by the GCM server during registration, and the code has been modified to re-try the registration process if a failure is encountered.

SR-A12537 · Issue 224733

Optimistic locking honors OfflineEnabled function

Resolved in Pega Version 7.2

After upgrade, if a top level case type rule was checked out through the Case Explorer by opening the Case Designer and then changing the locking mode to Optimistic, the value reset back to Default after check-in. This was an issue with the pyOfflineEnabled setting being honored, and has been corrected.

SR-A9893 · Issue 220141

Checkbox values retained in Hybrid client on iOS

Resolved in Pega Version 7.2

Checkbox property values were not retained in Hybrid client on iOS inside a repeating dynamic layout, displaying the checkboxes as unchecked even when the property associated with the checkbox had value = true. This was not an issue when running the application on a desktop or in a regular mobile browser. This was traced to the ID attribute value of all the checkboxes being rendered as the same in this circumstance, and the system has been updated to generate unique ID attributes if bOptimized is true in the pzGenerateCheckbox RUF.

SR-125113 · Issue 193442

Localized labels displaying in Safari

Resolved in Pega Version 7.2

Localized headers were not displaying properly on Safari browsers if the Fat List mode was used for the grid headers. Rendering worked as expected using Field Value mode. This was an issue with localized labels not rendering properly when the width of the Safari browser is reduced, and has been fixed. In addition, an issue with the header values being added dynamically instead of using constant values for a mobile browser grid using responsive mode has also been fixed.

SR-125113 · Issue 216785

Localized labels displaying in Safari

Resolved in Pega Version 7.2

Localized headers were not displaying properly on Safari browsers if the Fat List mode was used for the grid headers. Rendering worked as expected using Field Value mode. This was an issue with localized labels not rendering properly when the width of the Safari browser is reduced, and has been fixed. In addition, an issue with the header values being added dynamically instead of using constant values for a mobile browser grid using responsive mode has also been fixed.

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.

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