INC-173633 · Issue 650276
Google Key security updated
Resolved in Pega Version 8.6.1
Cross-site scripting protections have been added for Google Key.
INC-174435 · Issue 659480
Survey Complex Question Definition properly displayed
Resolved in Pega Version 8.6.1
Selecting any Complex Question to look at the definition displayed a blank screen. This was traced to an issue with the ruleformtabs properties for the layout group used by complex questions, and has been resolved by changing the Layout Group display type from "Default" to "Tab".
INC-175000 · Issue 657007
Handling added for Address Map control in Microsoft Internet Explorer 11
Resolved in Pega Version 8.6.1
Microsoft Internet Explorer 11 does not support Class, async, await and arrowed functions due to not implementing the necessary EC6 features. This caused Address Map Control to not work in this browser because pypega_map_googlegis js creates a js class. To resolve this issue, alternate methods have been added for use with Microsoft Internet Explorer 11.
INC-175684 · Issue 658698
Parameterized data pages updated on record change
Resolved in Pega Version 8.6.1
Changing source data page records without changing the parameter value was not updating parametrized data pages. This has been resolved by updating the system so the parametrized data page populator function is now called every time the page is accessed.
INC-180233 · Issue 660579
Offline.Rulecache UI module capacity increased
Resolved in Pega Version 8.6.1
Clicking the save button on a modal window caused the application to freeze and all the buttons were disabled. This was traced to the pega.offline.rulecache UI module having a default hard limit of 500 rules. Once the hard limit was reached, the system intermittently silently refused caching additional rules depending on the amount of rules packaged or the order in which the rules are loaded to the cache. To resolve this, the system has been updated to only log a console warning once the maximum threshold is reached, allowing the application to operate normally and at the time inform about the potential impact of having too many rules in memory.
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.