SR-D24470 · Issue 494628
Custom attachment category parameter passed to dropdown
Resolved in Pega Version 8.4
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.
SR-D24651 · Issue 495766
Proper assignment instructions sent when transferring
Resolved in Pega Version 8.4
Assignment instructions were not getting added properly when transferring to Workbaskets. Because both .pyInstruction and Param.InstructionNote are set in call Reassign (to workbasket), the same instruction value was being given twice. To resolve this, step 8 (Call Reassign) of Work-.pyReassignAssignment has been modified and will not send the InstructionNote param as instruction is already updated on the newassign page with the instruction value on reassign page in the previous step (step 7).
SR-D24950 · Issue 494567
Added explicit step page to resolve null-pointer exception with custom error message
Resolved in Pega Version 8.4
A null pointer exception was generated during case run time harness refresh after a custom error message was inserted. This was traced to a blank step page related to the custom message, and has been resolved by adding a primary step page at step 10 of the New(Work-) activity to prevent the null-pointer exception on harness reload.
SR-D26589 · Issue 496722
Formula properly evaluated in pxParseExcelFile activity
Resolved in Pega Version 8.4
When trying to use the activity pxParseExcelFile on an Excel file containing three sheets where each sheet had a different pagelist, the properties mentioned in sheet 1 were populated on upload but the remaining sheets only showed the error message "Could not get clipboard property for reference Work Queues.". This was caused by an error in Row index handling for the additional sheets, and has been resolved by updating the logic to populate the data in the clipboard.
SR-D29114 · Issue 499933
Added handling for bulleted text insert triggering audit
Resolved in Pega Version 8.4
When a bulleted text (copied from an email or rich text ) was used in the text area property, the audit considered it as a change even when there was no change. This was tracked to the field value 'pyHistoryMemo • ChangeTrack_Add' in @baseclass which is being used to get the localized value for audit memo: the field value accepts only 2 parameters, but the inserted text area input contained the '\t' that is used for parameter translation. To resolve this, the system will call the addMemoForSecurityChangeTracking utility method to replace all \t's present in both the Current Value and Previous value with 'empty' such that no '\t' characters are available in either of the string parameters.
SR-D29590 · Issue 499252
Local change given for Attachment List View alignment issue
Resolved in Pega Version 8.4
In the Attachment List View section, the text for the filter dropdown is misaligned and an extra close icon appears. As Attachment List View has been deprecated, this will not be addressed in a platform fix. For a workaround local change, add the below code in the AttachmentListView section: <style> .yui-panel .container-close::before, .container-close::before{ visibility:hidden; } #allCol{ width:155px; } </style>
SR-D30687 · Issue 500892
Update message clarified for manual case update after SmartEmail shape used
Resolved in Pega Version 8.4
For a case with #1 Optimistic Lock and #2 a SendEmail smart shape in the middle of a flow, once the SendEmail updated the case in the background, updating the case manually resulted in a "Please re-submit" message being displayed without any explanation. This has been resolved by ensuring that instead of a resubmit message (system update), the system will show a refresh message (normal update).
SR-D31751 · Issue 504653
SQL query performance improvement
Resolved in Pega Version 8.4
Multiple queries were being framed with an UPPER function in the 'where' clause, causing performance issues. Investigation showed that report definitions related to audit (i.e., pyGetWorkHistory and pyGetWorkHistoryWithLatLong) were enabled to retrieve records by ignoring case. To avoid this, the system will compute the correct class name and pass it to the report definitions.
SR-D37444 · Issue 507039
WorkBasketGadget control updated for improved backwards compatibility
Resolved in Pega Version 8.4
After upgrade, the WorkBasketGadget Control was not retrieving the work queues. This was traced to a backwards compatibility issue introduced when greater security was put in place. The control WorkBasketGadget contains a call to pzEncryptURLActionString that was introduced in 8.x versions of the platform to encrypt URLs to avoid hijacking. The content of the URL relies on the pxRequestor.pxWorkGroup property, which is resolved using pega:reference tags. This approach was working in versions below 8.x, but these tags were not resolved at runtime. To correct this, requestorWorkGroup will be resolved as string and passed as a parameter instead of using pega:reference tags.
SR-D39264 · Issue 518841
Multiple files uploaded using "select file" will be handled asynchronously
Resolved in Pega Version 8.4
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.