INC-144566 · Issue 600855
User lookup list correctly populated when using # tag
Resolved in Pega Version 8.6
When typing '#ANewTag @' in Pulse, the user lookup list was not shown. Using '#ExistingTag @' worked as expected. This was a missed use case in work done to improve the performance of pzJquerymentionsInput by restricting REST calls, and has been resolved.
INC-144948 · Issue 602274
Resolved JBoss memory leak
Resolved in Pega Version 8.6
JBoss logs indicated connection leaks. This has been resolved by limiting the scope of instance of ActionProvider, DataSyncRequestParser to a try-with-resources block which ensures that all resources are released.
INC-144970 · Issue 604953
Tags correctly displaying after Pega 8 Upgrade
Resolved in Pega Version 8.6
The context class for Tags was consistently picking up from the Access group but not consistently from the work class. This caused previously created tags in Pega 7 to not show up in Pega 8, and tags created through the Case Management->Social->Tag configuration were not showing up for user details. This was traced to several differences in the logic between the versions, and updates have been made to resolve this.
INC-145052 · Issue 604350
Survey Question Page enhanced to improve large question set performance
Resolved in Pega Version 8.6
When a survey was saved from survey designer authoring, all the questions within that survey were saved irrespective of whether the question was modified or not. This caused performance issues when there were more than 150 to 200 questions in survey. To resolve this, whenever a question is touched, a pyIsVisited flag will be maintained for each question and only those questions which have this flag set to true will be saved.
INC-145445 · Issue 606466
Added handling for Get Directions using http in mobile
Resolved in Pega Version 8.6
When attempting to use the Get Directions action from from a newly launched window in the mobile application, an error indicating the popup blocker was enabled appeared even though popup blocker was disabled. This was caused by the map being requested with http while the current protocol was https, and has been resolved by adding logic that will handle the map from https conditionally based on the current protocol.
INC-146114 · Issue 604412
Create Survey routes case correctly
Resolved in Pega Version 8.6
The Create Survey utility was not routing the case to the user who initiated the case, but instead was routing it to the user who checked-in the case. This was traced to an error related to pxRequestor.pxUserIdentifier in the data transform pzpopulate survey params which is called when the survey utility is used, and has been corrected.
INC-146676 · Issue 601941
Field Service app localizations updated
Resolved in Pega Version 8.6
Localization has been added to the 'getDirections' alert and other popup alerts in the Field Service app.
INC-148392 · Issue 610668
File type handling added for cloud downloads on mobile app
Resolved in Pega Version 8.6
When using the Pega cloud storage repository (Application -> Integration -> Content Storage) with the mobile app, it was possible to upload attachments but re-downloading the attachments failed. Investigation showed that this was due to the content-type appearing as application/* so the file type was not able to be identified. This was a missed use-case for returnFileForDownload(), and has been resolved.
INC-148657 · Issue 607571
Check added for invalid operatorID set by autopopulate
Resolved in Pega Version 8.6
When an SLA rule attached email reminders, the Link-Attachment table saved the creating operator as System. Upon opening the case perform in Cosmos, all attachments were shown in the utility area and the system tried to show the user name using the pyUserDetails linked property, causing the assignment system to generate a "System is not valid operator" error and the case open failed. To resolve this, the system has been updated to avoid setting the error message on Datapage if an invalid operatorid is passed.
INC-150578 · Issue 607478
RTE control handling updated for survey display text
Resolved in Pega Version 8.6
After upgrade, Display text in the survey was missing for the question rules which used Rich Text Editor control. This has been resolved by updating the system to copy DisplayText and QuestionText into DisplayTextWrapper.