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-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.

SR-D51535 · Issue 519475

Enhanced discrimination for tasks in MyPega spaces

Resolved in Pega Version 8.2.6

When using My Pega for spaces and tasks, using drag and drop to move many cases around quickly resulted in tasks intermittently ending up in a state where they could not be updated further and became unusable. Analysis showed that because the milliseconds part of the update time was rounded, the logic of comparing for value between 0 and 1000 failed when the comparison returned -ve value. To resolve this, the comparison has been modified to !=0 and the 'when' rule pyContinueTaskProcessing has been added as an extension along with the appropriate usage guide to restrict processing. By default, the system will consider task name, description, due date, assignee, and rank properties; if more properties are needed to evaluate, this when rule can help.

SR-D59482 · Issue 521508

Corrected generated Excel saving decimal values as text

Resolved in Pega Version 8.2.6

When using RDB-List to fetch the data from the database for the clipboard and then using pxGenerateExcelFile to generate an excel file from that with a provided RFB template file, some decimal properties were stored in text format instead of numeric. This has been resolved by updating the API.

SR-D59504 · Issue 524642

Attachment drag drop searches only current Ajax context

Resolved in Pega Version 8.2.6

When the Interaction for customer service was open and more than 1 task from the sidebar was open, the drag and drop zone was missing on any subsequent Task/Cases past the first. In an Ajax container scenario, getElementByID js was searching in all the containers because they were present in DOM, and it was losing context. To resolve this, the code has been updated to only search in the current context when using an Ajax container.

SR-D63976 · Issue 524221

Double decompression of Attachment BLOBs corrected

Resolved in Pega Version 8.2.6

Attachment streams were being double-decompressed on download. This was traced to the GetAttachmentReference activity in which the file was opened then performing a show-html of DisplayAttachment HTML. This internally called the DisplayAttachFile activity which attempted to open the file again, resulting in a double de-compression of the attachment BLOB. This has been corrected.

SR-D64506 · Issue 529335

Improved accessibility around page landmarks

Resolved in Pega Version 8.2.6

Accessibility testing revealed an issue with pages where the main landmark was contained in another landmark. This has been resolved by removing the main role in the FlowActionHTML rule.

SR-D65513 · Issue 530182

URL encryption modified for ShowAllOperators

Resolved in Pega Version 8.2.6

In the control ShowAllOperators the call to pzEncryptURLActionString was introduced to encrypt URLs to avoid hijacking. The content of the URL relied on the pxRequestor.pxWorkGroup property which was resolved using pega:reference tags. This approach worked in versions below 8.x, but in higher versions the tags were not resolved at runtime and results were not displayed. To resolve this, the requestorWorkGroup will be treated as string and passed as parameter instead of using pega:reference tags.

SR-D72886 · Issue 543754

Check added for Repositories before saving attachment

Resolved in Pega Version 8.2.6

When creating or updating a case through email listener, the Link-Attachment defaulted the pxStorageType to 'WebStorage'. This caused an issue when using PegaS3, which needs pxStorageType 'Repository'. To resolve this, a check has been added to see if Repositories are enabled, and if they are the storageType will be set accordingly.

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