INC-190384 · Issue 676573
URL validation updated to handle custom token endpoints
Resolved in Pega Version 8.7
While saving an authentication profile with OAuth details, validation was failing for a valid URL given in the access token endpoint and revoke token endpoint fields. This was traced to the use of the Apache URL validator, which considered some domains to be invalid. To resolve this, the urlvalidator constructor has been updated to include a custom RegexValidator for access token and refresh token URLs.
INC-166995 · Issue 642440
DeleteDocumentPg added to allow list
Resolved in Pega Version 8.7
During performance testing with CSRF settings enabled, a '403 Forbidden' error was seen in the network trace when FinishAssignment called pyActivity=pyDeleteDocument on close action. This has been resolved by adding pyDeleteDocumentPg to the list of allowed activities.
INC-190417 · Issue 675213
ModifiedGetEmailPosts data transform to better handle very large messages
Resolved in Pega Version 8.7
Blank emails were seen when the message was over 4000 characters. This was traced to an issue with initializing param.index2, and has been resolved by modifying the pxGetEmailPosts data transform to take param.index2=0 out of the loop for large emails.
INC-189819 · Issue 676594
Entity highlight corrected
Resolved in Pega Version 8.7
In the email channel, the entity value highlighted under "Training" tab was different from the actual value detected. The location where it was detected was also different. This was traced to an inconsistency of the title shown on the UI of training data tab, and has been resolved by updating the title shown on each entity as well as using exit iteration instead of skip step in pyStructureEntity.
INC-185251 · Issue 674906
Locking APIs updated to handle CDK key rotation
Resolved in Pega Version 8.7
it was not possible to save cases for several hours following the CDK key rotation. This was traced to an exception that caused the system to attempt to acquire a lock on the CDK key instance, and normal save behavior would resume after the default sys lock time out period expired. This has been resolved by updating the system to use LockManager APIs to perform a database save with locks.
INC-185455 · Issue 671977
Email widget auto-refreshes for incoming email
Resolved in Pega Version 8.7
The email thread was not updated automatically for incoming email in an email interaction case with Outlook, but did refresh when the work object was closed and opened in perform mode. This was traced to a Jump statement after pyMapEmailToEmailTriage which interfered with threading, which has now been removed.
INC-180594 · Issue 670957
Filtering added for DisableDormantOperators
Resolved in Pega Version 8.7
When running the Disable Dormant Operators agent, many operators were seen which were dormant but not disabled. Investigation showed the activity was fetching all of the operators without filtering the deactivation state. This has been resolved by adding a filter condition in pzDisableDormantOperators to fetch only deactivate state users.
INC-154254 · Issue 674945
Correct Email Bot training text highlighted
Resolved in Pega Version 8.7
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-193727 · Issue 679111
Entity mapping order updated for email bot
Resolved in Pega Version 8.7
Issues were seen with the entity mapping functionality in Email bot, especially when mapping email headers like subject, from (email) etc. to case properties. This was an issue with the order in which the entities were mapped ,and has been resolved with an update that will map entities which are configured in the channel first and then mapping the rest.
SR-D32991 · Issue 504130
Email Discussion Thread retains Formatting
Resolved in Pega Version 8.2.4
CSS styles were not being retained in the discussion thread when replying to InboundCorrespondence cases. This was traced to a missing value in Param.latestReply activity pzCreateExternalPostFromMail, and has been resolved by setting an initial plain text value to the param.latestReply before it is set with the HTML value. This prevents having a blank parameter value if the incoming HTML value is empty.