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.

INC-128960 · Issue 571360

Corrected approval step task message

Resolved in Pega Version 8.1.9

When a case progressed to the approval step, the task name did not properly appear as part of the "Please approve or reject this" message. In another scenario, a portal which supported locale switching was not translating "Please approve or reject this" when the locale was switched, but instead displayed the message in the original language. Investigation traced this to the pzInstructionsForApproval data transform storing the localized field value, causing it to persist inappropriately. This has been resolved.

INC-131151 · Issue 572832

Resolved empty body for Reject email

Resolved in Pega Version 8.1.9

When using the pzEmailActions Section in Correspondence for Approve/ Reject functionality via email, there was no reply body in the email for Reject Option. This was due to the flow action for the Reject email being different than that of the Approve email, and has been resolved.

INC-131385 · Issue 573454

Swagger APIs updated

Resolved in Pega Version 8.1.9

The Swagger File APIs have been updated to ensure swagger document files generated meet specifications for editor.swagger.io .

INC-134370 · Issue 577635

Expanded Grid locking updated

Resolved in Pega Version 8.1.9

When using pyDashboadMyWorkList to show the cases of an operator with Master Detail in Read Only mode, the system was acquiring a lock on the expanded work object. To resolve this, the following changes have been made: * In activity Assign-pyAcquireObject, If the parameter bRODetails is true, do not call acquireWorkObject and do obj-open-by-Handle to get assignment and work page in pyAcquireObject activity. * In activity acquireWorkObject, the parameter skipWorkLock has been removed as acquireWorkObject should always acquire the lock.

INC-134709 · Issue 579433

Updated endpoint Cross-site scripting protection

Resolved in Pega Version 8.1.9

Cross-site scripting security has been updated for Endpoints in Display activities.

INC-140739 · Issue 592830

UniqueID enhancement for attached files

Resolved in Pega Version 8.1.9

When two files with the same name were uploaded by different users simultaneously through Pulse or if a user uploaded two files with the same name across two sessions, whichever file arrived later was overriding the previous one in the system. As a result, the first pulse post ended up with an incorrect file attached. This has been resolved with an enhancement to add an API that appends a uniqueID to the file before uploading to ServiceExport directory.

SR-D98224 · Issue 580595

Updated endpoint Cross-site scripting protection

Resolved in Pega Version 8.1.9

Cross-site scripting security has been updated for Endpoints in Display activities.

SR-D39264 · Issue 518840

Multiple files uploaded using "select file" will be handled asynchronously

Resolved in Pega Version 8.2.6

In order to resolve an intermittent error when uploading multiple files using the "select file" button, each file will be uploaded asynchronously to avoid overloading the browser threshold.

SR-D47146 · Issue 515648

Pick Values modal updated for deprecated list view handling

Resolved in Pega Version 8.2.6

Pick values were not displaying in the menus below Case Management-> Tools -> My Work, including "Work entered by me", "Work by workbasket", and "Work resolved by me recently". This was due to the use of deprecated list views: the pick values modal was failing to show and hide the busy indicator because the indicator now uses jQuery, but list view does not include jQuery. In order to resolve this, the equivalent Report Definition pyEnteredByMe has now been added under the navigation rule : pzProcessAndCaseRulesMainMenu.

SR-D48242 · Issue 513541

Export to Excel cell style control added for Case Management

Resolved in Pega Version 8.2.6

If a column were formatted with an auto generated numeric control, a new cell style was generated for every row during the Export to Excel process. Since there is a limit on the amount of cell styles, once the number of rows in the file was greater than 64000, an error was generated. To resolve this, the system will disable the creation of a new cell style for every instance when an auto-generated numeric control is used for Export to Excel in Case Management.

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