SR-116508 · Issue 170253
Large flow handling improved for IE8
Resolved in Pega Version 7.1.7
When opening a large flow in IE8 which includes multiple sub flows, a long-running script warning is displayed. This is caused by too many calls being executed at once on IE8, and has been remedied by turning on the asyncProcessing parameter for IE8.
SR-116818 · Issue 167121
Corrected swim lane routing with shapes
Resolved in Pega Version 7.1.7
While using swim lanes, adding shapes into the flow caused unexpected and random behavior of the process modeler including failure to return control to the user after saving. This error was related to routing handling when swim lanes are present, and has been corrected.
SR-117228 · Issue 168249
Resolved issues with Flow shapes distributed across Swim Lanes
Resolved in Pega Version 7.1.7
Pool size is maintained as both pixels and inches, but auto conversion was failing if the pool dimension was very large. This created an error where saving a flow rule could cause the pool to drastically shrink (for example, 20 inches becoming 20 pixels). In order to maintain the proper dimensions, a check has been added for pool and swimlane to ensure the proper inch/pixel conversions.
INC-147654 · Issue 642188
Updates to displaying embedded images in cases
Resolved in Pega Version 8.5.4
Sending an email with an embedded image to the email ID associated with the email listener successfully created the interaction case, but the embedded image was not displayed when the case was opened from the work-basket. A rule-not found exception was seen in the tracer for pyGetImageDisplay, the rule responsible for displaying the images in the ET pane. Investigation showed that when URLObfuscation was turned on, the decryption of the URL was not successful because "&" had been encoded to '& amp;'. This has been resolved by calling the activity pyGetImageForDisplay using URLMapping instead. An additional issue was seen with displaying images in the email interaction pane where the additional empty new lines moved the image outside the intended place. This was traced to a customization for the reply area which used the pyHighlightedMessage property and converted newlines to br tags even in HTML mode. To resolve this, pyHighlightedMessage has ben modified to convert newlines to br tags only if the mode is plain text.
INC-157214 · Issue 631599
Mentioned user in Pulse appears correctly
Resolved in Pega Version 8.5.4
When loading user names while using the "@" functionality in a Pulse post, adding or tagging the operator/user in Pulse by entering each letter brought up the list, but when using copy/paste it was not possible to select the desired value from the user.Suggestions list of operators/users. If by chance the user name was selected from the suggested list, the operator ID was added instead of the full name. This has been resolved.
INC-160372 · Issue 629921
Resolved unneeded chat survey error logging
Resolved in Pega Version 8.5.4
After configuring a chat server to do a post chat survey, the post chat survey was correctly served but errors indicating "Cannot find PegaCA-Work-SurveyNPS.Thank you for your feedback. van type Rule-HTML-Paragraph" were logged. This was caused by the method used by the system to distinguish between text and paragraph questions in pyProcessNextStep, and has been resolved by adding additional checks for whether paragraph exists before opening it.
INC-160688 · Issue 632229
Skip topics from the attachments setting honored
Resolved in Pega Version 8.5.4
Topic detection was happening for attachments even when it was disabled in the UI. This issue was traced to pyTopics which were not properly configured by selecting checkboxes in iNLP configuration for Email Channel, and has been resolved.
INC-163368 · Issue 634469
Special character replacement added for Email Bot training data
Resolved in Pega Version 8.5.4
When training an Email bot in the email channel, the training data was incorrectly added to the model. Although the text was tagged as an entity in the channel and highlighted correctly, after building the model it was seen that the tagged text contained dislocated start and end tags. Investigation showed that this occurred If the training data text had \r's in it. To resolve this, updatetrainingrecord has been modified to replace \r 's with "". The text which is being replaced will not appear in the UI.
INC-165188 · Issue 635776
Third-party links allowed to pass target attribute in anchor
Resolved in Pega Version 8.5.4
Attempting to connect to Docusign, a third party application, via Email in an interaction portal was not working, and the error "account.docusign.com refused to connect" appeared. This was caused by the HTML data being sanitized so the attribute 'target' was not allowed to pass and the application could not open in a new tab. To resolve this, an update has been made that will allow the target attribute for an anchor tag.
INC-165886 · Issue 637243
JWT token support added for Digital Messaging
Resolved in Pega Version 8.5.4
An enhancement has been added to support the use of JWT tokens for authentication with the Digital Messaging API.