SR-D18853 · Issue 488283
Visibility on client check removed to enable Pulse on click
Resolved in Pega Version 8.3.1
When Pulse was configured on click of a icon, the comment section was not visible. Investigation showed that at the time of DOM load, pyMessage property was not available in the DOM because 'Run visibility condition on client' was checked by default. Visibility on client checks have been removed to resolve this issue.
SR-D37757 · Issue 507966
Pulse delete icon repaired
Resolved in Pega Version 8.3.1
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-D44012 · Issue 509880
Added more error handling in pzCreateThumbnail
Resolved in Pega Version 8.3.1
In activity pzCreateThumbnail, a null pointer error was generated at step 2. This was traced to the value of originalImage being null even though there was no error in the image file itself, and has been resolved by adding an error check .
SR-D17575 · Issue 489953
Survey route to work queue option restored for smartshape
Resolved in Pega Version 8.3.2
After upgrade, routing to workqueue was no longer available for the new create survey smart shape. This has been restored.
SR-D37275 · Issue 519026
Enabled PDF attachment for iPad Safari
Resolved in Pega Version 8.3.2
It was not possible to select the PDF option when attempting to attach a file while using iPad Safari. This has been corrected.
SR-D40605 · Issue 510916
Corrected mobile password control behavior on failed validation
Resolved in Pega Version 8.3.2
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-D42243 · Issue 525771
Added handling for offline mobile attachments using PRFiles and Repositories
Resolved in Pega Version 8.3.2
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 513647
Pulse @mention will avoid triggering search request if no suggestion list is available
Resolved in Pega Version 8.3.2
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.
SR-D43272 · Issue 516439
Local user lookup modifed to use requestor level data page to improve performance
Resolved in Pega Version 8.3.2
In a system with many users (over 40k), attempting to search for a user to send a private message was taking an excessive amount of time. Analysis found that all of the users were being loaded at once in a page list of type Code-Pega-List. This led to errors indicating the Page List property had more elements than the specified threshold, but pagination could not be added as the activity and RD are final. To improve performance, this process has been modified to use a data page at the requestor level instead.
SR-D43808 · Issue 512660
Resolved loop causing search to fail
Resolved in Pega Version 8.3.2
After upgrade, searching for a case caused node failure. This was traced to a system loop when trying to remove duplicate workpool classes and has been resolved by updating the pyPopulateWorkPoolsAndClassesForTagsSearch activity to remove extra looping on workpool classes in step 3. In addition, a new 'when' rule pyIsTagSearchEnabled has been added: the pySearchWrapper activity will only search tags when this rule is true.