INC-146521 · Issue 602657
Survey Question Page Radio/Dropdown Button retains value
Resolved in Pega Version 8.3.5
After creating an Interaction from the portal and selecting "Survey", the Survey Question Page using a Radio button/Dropdown button as Question did not retain the value after a selection was made. This has been resolved by modifying the refreshSurvey method in pzsurvey_ui_userscript.js to work with an Ajax container.
INC-144311 · Issue 601109
Updates for nested "Append And Map To"
Resolved in Pega Version 8.3.5
Nested actions "Append And Map To" in Data Transforms were producing incorrect results when offline. This was traced to all operations being performed on the Page List which was on first level of nesting, which was caused by changing the Data Transform into JavaScript form for offline use. The JavaScript form of DataTransform uses variable the "targetListObj" to represent the Page List, and this same name was reused regardless of the "Append And Map To" nesting. An additional problem was seen with the "Update Page" Data Transform action when used with conjunction with a nested "Append And Map To" action: the action assumes that top level Pages exists, but "Update Page" did not create them. This caused the "Append And Map To" action to fail. To resolve this, the "Append And Map To" action will use suffixed variable names to reference nested PageLists, and "Update Page" will create the Page if it doesn't exist.
INC-144566 · Issue 600857
User lookup list correctly populated when using # tag
Resolved in Pega Version 8.3.5
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-154254 · Issue 632638
Correct Email Bot training text highlighted
Resolved in Pega Version 8.4.6
When a piece of text was selected and tagged against an entity while training the Email Bot, the entity selection was misplaced and partially covered the actual text selected. The incorrect selection was then carried forward to the training data spreadsheet. To resolve this, rule changes have been made that will update HTML entities to HTML encoded forms.
INC-175994 · Issue 667483
Removed redundant Microsoft Outlook email interaction chain
Resolved in Pega Version 8.4.6
When opening an email interaction case, the email editor user interface area showed the complete email chain of the email for every new message that came in related to the case. This was traced to the difference in the selectors that various email clients use to construct a response to an email with email history in it, and has been resolved by updating the selectors for Microsoft Outlook in pyRichTextEmailHistorySelector so no conversation is repeated when using that client.
INC-187031 · Issue 676245
Topic handling updated for behavior tab
Resolved in Pega Version 8.4.6
While submitting topics configured on the behavior tab of the chat channel, duplicate records were created and a null pointer exception was generated. Investigation showed this was due to a difference in Topic handling between the email channel and the chat channel in a modal window, and has been resolved.
INC-180233 · Issue 660577
Offline.Rulecache UI module capacity increased
Resolved in Pega Version 8.4.6
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.
INC-181126 · Issue 663304
Signature Accept callback fires correctly in offline app
Resolved in Pega Version 8.4.6
Clicking on the Accept button in the Pega mobile signature control was not properly calling the necessary pega.ui.signature.acceptSignatureCallback method. This has been resolved by adding code for the Post Success and Failure callback on Signature accept in the offline app.
INC-183559 · Issue 664815
Handling added to process Actions chunks on multiple nodes
Resolved in Pega Version 8.4.6
If the synching of chunks to a node was interrupted, attempting to resume the remaining chunks resulted in a processing issue if the Load Balancer passed the connection to a different node than was used for the first connection. As an example, if chunks were synched to node "A" and the restarted sync saved the remaining chunks to node "B", when all chunks were synced node "B" incorrectly determined node "A" was actually doing the work and skipped the processing of the chunks on node "B". This resulted in queued chunks being left untouched. To resolve this, the logic has been updated to allow multiple nodes to process the chunks.
INC-183864 · Issue 666188
Updated RequestorInitialize to improve performance
Resolved in Pega Version 8.4.6
After updating, initial user logins were taking an excessive amount of time. This was traced to the standard rule "RequestorInitialize", and has been resolved by updating the implementation.