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.

INC-171446 · Issue 649616

Updated logic for setting param.PrimaryPage in transfer

Resolved in Pega Version 8.4.5

TransferAssignment was failing intermittently when doing routing either by background processing or manual transfer. Investigation showed this was caused by a null param.PrimaryPage value which resulted in a NullStepPage exception. This has been resolved by adding a Property-Set method just before calling the activity pxTransferAssignment.

INC-172683 · Issue 652827

Check added to set class for inheritance if Work- is not present

Resolved in Pega Version 8.4.5

Bulk Action transfer was not working for Assignments from Data class. Investigation showed that when the interest page class inheritance did not contain Work-, flow action pyTransferAssignment was not able to render as it is present in Work- layer. To resolve this, a check has been added to the pyGetRelevantActions so that if the interest page class inheritance doesn't contain Work-, the case class will be set from the workobj page.

INC-175630 · Issue 653865

Application selections only announced when visible

Resolved in Pega Version 8.4.5

The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.

INC-176091 · Issue 652122

Busy indicator correctly resolves with Microsoft Internet Explorer upload

Resolved in Pega Version 8.4.5

When using Microsoft Internet Explorer to upload documents, the busy indicator was not resolving after the file was attached. This was due to a missed use case in work done around the timing of the busy indicator when attaching multiple files, and has been resolved by modifying PzMultiFilePath to ensure the busy Indicator is removed when the file count is zero.

INC-177183 · Issue 656492

Refresh assignment checks updated

Resolved in Pega Version 8.4.5

Additional privilege checks have been added to refresh assignment.

SR-D47146 · Issue 515647

Pick Values modal updated for deprecated list view handling

Resolved in Pega Version 8.1.8

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-D59504 · Issue 524641

Attachment drag drop searches only current Ajax context

Resolved in Pega Version 8.1.8

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-D76291 · Issue 547842

Updated retry logic for S3 AddAttachmentFromEmail

Resolved in Pega Version 8.1.8

When using the AddAttachmentFromEmail activity with S3 repositories, performing an obj-save on the data-workattach-file page executes a deferred save while also saving the file into the repository. if the data was inserted into S3 successfully but encountered an issue when saving the related data-work-attach-file page, the system was trying to call the save operation again. This tried to insert the duplicate attachment again to S3, causing an error on that side of the process. To resolve this, the duplicate Obj-Save functionality in AddAttachmentFromMail Activity has been removed.

SR-D80120 · Issue 544216

Custom attachment category parameter passed to dropdown

Resolved in Pega Version 8.1.8

Attempting to use the out-of-the-box “Attachments control” which was configured at design time to use a custom category where both the custom category and the section class were in the same work class resulted in the attachment category dropdown defaulting to “File” instead of the custom category. Investigation showed that the custom attachment category name configured on the control was missing in one of the pre-processing activities sequence. To resolve this, the activity Work-.pzInitAttachContent and the initAttachmentPage activity have been updated to pass the custom attachment category parameter.

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