SR-A10040 · Issue 219561
Section refresh added to Integrator shape
Resolved in Pega Version 7.2
The Integrator shape in Data class was not showing parameters in the properties screen. A section refresh has been added to "pzIntegratorTab" that will be triggered upon selection of the rule in the integrator
SR-A10040 · Issue 219304
Section refresh added to Integrator shape
Resolved in Pega Version 7.2
The Integrator shape in Data class was not showing parameters in the properties screen. A section refresh has been added to "pzIntegratorTab" that will be triggered upon selection of the rule in the integrator
SR-A12450 · Issue 223679
Trailing line removed from breadcrumb
Resolved in Pega Version 7.2
When creating a work item, the breadcrumb showed a trailing line when it displayed "Review and Confirm". This was an issue with a page change class in middle of a screenflow, and has been fixed.
SR-A12537 · Issue 224734
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-A13730 · Issue 226426
Localization added to pyWaitLabel and pyInstructions
Resolved in Pega Version 7.2
The Rule-Obj-Activity Dependency of class 'Work-' was creating pyWaitLabel and pyInstructions which were not localized. This has been fixed.
SR-A6996 · Issue 215315
Localization added to pyWaitLabel and pyInstructions
Resolved in Pega Version 7.2
The Rule-Obj-Activity Dependency of class 'Work-' was creating pyWaitLabel and pyInstructions which were not localized. This has been fixed.
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.