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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-D67316 · Issue 541204

Cross-site scripting protection for PegaRULESMove_Skimming_Query

Resolved in Pega Version 8.3.2

Cross-site scripting protection has been added for input parameter toRSV of the activity PegaRULESMove_Skimming_Query.

SR-D69927 · Issue 537484

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-D71475 · Issue 538720

Check added to apply values of newAssignPage.pxFormName

Resolved in Pega Version 8.3.2

After upgrade, trying to open existing assignments resulted in a different harness being opened. This was traced to changes in how the property newAssignPage.pxFormName was used, and has been resolved by checking whether the harnesspurpose is dynamic before setting the pxFormName. If formname is already present, the system will proceed with picking the harness from the shape.

SR-D72672 · Issue 536386

Security updated for CreateOperator

Resolved in Pega Version 8.3.2

In order to improve security, CreateOperator in Pega-ProCom will require authentication to run with pxCanManageUsers privilege.

SR-D75469 · Issue 538119

Resolved null-pointer exception in Expression Builder launch from activity rule

Resolved in Pega Version 8.3.2

A NullPointerException occurred in SafeURL when trying to launch the Expression Builder from an activity rule. This was trasced to a failure to get a value property in a target field due to the target element and its parent element containing the same value for name attribute. This caused the parent element to be considered instead of the target element. To resolve this, the search for the target element in parent tag will use '$p' along with 'target element name' in query selector.

SR-D75835 · Issue 539301

Added handling for Google Chrome drag and drop of Outlook email

Resolved in Pega Version 8.3.2

Attempting to drag and drop an email from Outlook to a case opened in Google Chrome resulted in the email being moved to the Outlook deleted folder. This was traced to Google Chrome defaulting to defining the "dropEffect" attribute as "none" when the expectation is it should be "copy". To resolve this, the recommended handling from Microsoft has been added as an event to make a copy (and not a move) an email from Outlook when dragged and dropped with Google Chrome.

SR-D17575 · Issue 489953

Survey route to work queue option restored for smartshape

Resolved in Pega Version 8.3.2

After upgrade, routing to workqueue was no longer available for the new create survey smart shape. This has been restored.

SR-D37275 · Issue 519026

Enabled PDF attachment for iPad Safari

Resolved in Pega Version 8.3.2

It was not possible to select the PDF option when attempting to attach a file while using iPad Safari. This has been corrected.

SR-D40605 · Issue 510916

Corrected mobile password control behavior on failed validation

Resolved in Pega Version 8.3.2

Given a section on mobile where the out-of-the-box password control was used on a textbox with input field of type Password to set a new password, failed validation on the field caused the cursor on the input field to jump to the left. It was then not possible to delete the text or correct the placement of the cursor. This was traced to a missing type check for password in isTextBox(), and has been corrected.

SR-D42243 · Issue 525771

Added handling for offline mobile attachments using PRFiles and Repositories

Resolved in Pega Version 8.3.2

Attaching a file on mobile and then immediately clicking on it to open it either did not open the attachment or the attachment opened and then the app stopped working with a "Sync Failed" error. Attachments were not synchronized on the server, and when synchronization was re-tried the attachment was duplicated on attachment list. This was traced to the system being configured to use PRFile API for synchronizing attachments along with Repositories to store attachments; when the processing "commitAttachment" action was processed, it called the Work-.AttachFile activity to finalize attachment upload, but the activity was called without the mandatory attachment InputStream required when using PRFile + Repositories. This has been resolved by ensuring there is a call to Work-.AttachFile with InputStream in cases where PRFiles and Repositories are enabled.

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