SR-D33930 · Issue 507972
Check added to pyWorkPage before context page replacement
Resolved in Pega Version 8.4
When given an assignment configured with Save and Next buttons where the on-click of the Next button triggered FinishAssignment and the case type used Optimistic locking, the workobject lock was not acquired and an error was thrown when clicking Save and then the Next button. Investigation showed that the lock was not acquired because the pyCaseUpdateInfo page was not available in the work object under pyWorkPage. This was traced to the 'When' condition used to display the delete icon on a pulse post. This When condition needs to be evaluated on the context page (in this case, the work page), but when multiple posts are present on the WorkObject) the pyWorkPage was being replaced with a fresh copy from the DB and any updates on the current work page were lost. To resolve this, the behavior has been changed from always creating a context page to only creating the context page if one does not already exist on the Thread.
SR-D35434 · Issue 504588
Added subprocess cleanup for hasPreviousTask loop
Resolved in Pega Version 8.4
The mobile app hung on a specific scenario where there were no displayable shapes in the flow path (all decision shapes) and the pyFlowPath became empty but wasn't removed from the pxFlow page. This was traced to environmental loops present in the application, and this has been resolved by ensuring that while going back, completed subprocesses are completely removed from the pxFlow on pyworkpage.
SR-D37033 · Issue 511461
Filter popup misalignment on grid corrected
Resolved in Pega Version 8.4
After clicking on a grid filter, the filter popup had two scrollbars for adjustment and did not stay on the grid while scrolling the screen. This has been fixed by modifying the CSS style of overflow, which was previously using one that was meant for tablets and which affected position calculation for overlays in touchable laptops.
SR-D37117 · Issue 511358
Update Survey Work Objects' utility differentiates between survey and other objects
Resolved in Pega Version 8.4
Running the Update Survey work object utility calls the “pxUpgradeSurveyProperties” datatransform, which has a 'when' rule to call the function “@pzSurveyUpgradeSetProperty” to replace the Questionnaire page in the first step. This function was failing with a logged exception when it was passed a string instead of the page it was expecting. This issue occurred when the WO did not have survey data structure, and was due to the Survey Utility being intended to upgrade only Pega Survey class instances. In order to allow for more flexibility, the Survey Upgrade Utility has now been enhanced to differentiate between survey and other objects to resolve the exceptions.
SR-D37275 · Issue 519029
Enabled PDF attachment for iPad Safari
Resolved in Pega Version 8.4
It was not possible to select the PDF option when attempting to attach a file while using iPad Safari. This has been corrected.
SR-D37757 · Issue 507968
Pulse delete icon repaired
Resolved in Pega Version 8.4
After upgrade, it was no longer possible to delete one's own comment in Pulse. This was traced to the section pzDeleteMessage having two dynamic layouts with icon as image configured. During runtime, this section was present in the DOM yet the icons were not visible when the conditions configured were returned as true. This was caused by an error in the generated java for the layout, and has been corrected.
SR-D40605 · Issue 510918
Corrected mobile password control behavior on failed validation
Resolved in Pega Version 8.4
Given a section on mobile where the out-of-the-box password control was used on a textbox with input field of type Password to set a new password, failed validation on the field caused the cursor on the input field to jump to the left. It was then not possible to delete the text or correct the placement of the cursor. This was traced to a missing type check for password in isTextBox(), and has been corrected.
SR-D42193 · Issue 515627
Color codes will not be saved as message tags
Resolved in Pega Version 8.4
When the pxCreateAndManageTriageWork activity created pulse message (M-) Cases that included the inbound email body message, it called the pySaveTagsInPost activity to save any tag references in the post message by using the pyObject property value. In some scenarios where the message content was from a mail client which embedded style color codes with “#” (eg: #B5C4DF), Pega identified those values as tags and added those tags to the pulse message. To resolve this, the system will format the message text before parsing it to save tags.
SR-D42243 · Issue 525773
Added handling for offline mobile attachments using PRFiles and Repositories
Resolved in Pega Version 8.4
Attaching a file on mobile and then immediately clicking on it to open it either did not open the attachment or the attachment opened and then the app stopped working with a "Sync Failed" error. Attachments were not synchronized on the server, and when synchronization was re-tried the attachment was duplicated on attachment list. This was traced to the system being configured to use PRFile API for synchronizing attachments along with Repositories to store attachments; when the processing "commitAttachment" action was processed, it called the Work-.AttachFile activity to finalize attachment upload, but the activity was called without the mandatory attachment InputStream required when using PRFile + Repositories. This has been resolved by ensuring there is a call to Work-.AttachFile with InputStream in cases where PRFiles and Repositories are enabled.
SR-D42437 · Issue 513649
Pulse @mention will avoid triggering search request if no suggestion list is available
Resolved in Pega Version 8.4
Search threads were causing requestor Lock Exceptions due to poorly optimized queries sent to ElasticSearch when a Pulse mention was attempting to look up a person (e.g. "@"+typing) and the search of case objects to match to that search were performing poorly. To resolve this, an update has been made to avoid triggering requests if the suggestions list is not available for the search query.