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.
SR-D40593 · Issue 513439
Extra spaces removed in Automation field value generation
Resolved in Pega Version 8.4
The control StatusLookUp was generating extra spaces in the field value DOM, causing issues with Automation. This has been corrected.
SR-D42244 · Issue 507486
Top page reference made explicit for alternate stage visibility condition
Resolved in Pega Version 8.4
After upgrade, trying to use Save-As on the caseType rule to move it to a higher Ruleset version resulted in the alternate stage configuration setting not showing correctly. This was due to the "set Value" action not being performed correctly when the save-as was performed, causing the client visibility condition on the DL cell which included the master details section to not be shown. This has been corrected by ensuring there is a proper reference to the top page in this scenario.
SR-D43807 · Issue 512048
Localization added to File upload alerts
Resolved in Pega Version 8.4
When uploading files as part of adding attachments, error and warning messages were displayed as alerts in English despite using localization. This was traced to the pzMultiDragDropControlStandard control rule having the HTML alert messages hard coded instead of using field values which could be localized. To resolve this, field values have been created for the messages related to DragDropMaxSize, FileNotExistMessage, FileUploadSupportMessage, and UnableToLoadFileMessage.
SR-D47018 · Issue 517033
Corrected parameter being encrypted during change portal configuration
Resolved in Pega Version 8.4
After configuring a changePortalLayout control using .pyDescription as property, trying to switch the portal was throwing a error page. The same configuration worked in earlier platform versions. This was traced to recent updates where the activity parameter ended up being encrypted along with the activity name, and has been resolved by removing the parameter from encryption input and adding it to encryption output.