SR-A12980 · Issue 227344
Added dropdown to select applications for new requirements
Resolved in Pega Version 7.2.1
A dropdown has been added to the Requirements screen to display the existing applications for the current user when creating new requirements.
SR-A20072 · Issue 238701
Portal markup in PDF resolved
Resolved in Pega Version 7.2.1
When using the Google Chrome browser, the portal harness markup was being included in PDFs generated from the user portal due to the frameless dynamic container. This has been corrected.
SR-A20094 · Issue 238591
Localization handling updated for High Level Overview documents generated in Word
Resolved in Pega Version 7.2.1
In a localized environment, High Level Overview documents generated in Word included some garbled characters if there were images or attachments in between the content of sections. The localization code has been updated to properly handle this format.
SR-A20183 · Issue 238612
Localization handling updated for High Level Overview documents generated in Word
Resolved in Pega Version 7.2.1
In a localized environment, High Level Overview documents generated in Word included some garbled characters if there were images or attachments in between the content of sections. The localization code has been updated to properly handle this format.
SR-A21569 · Issue 242079
Corrected persistence of deleted requirements links with multiple actors
Resolved in Pega Version 7.2.1
When checking in a specification with more than one actor specified on it, deleted requirement links re-appeared after the rule was closed and re-opened. This was due to an unnecessary section refresh, which has been removed.
INC-143320 · Issue 602281
Support added for email addresses with hyphen in domain name
Resolved in Pega Version 8.3.5
When attempting to enter a email with a hyphen '-' in the domain part of an email ID ([email protected]), the reply button was getting disabled. This was caused by the regex validation implemented in the "pzValidateEmailAddress" (Work-Channel-Triage-Email) standard activity not covering all the possible cases. To resolve this, regex has been changed to instead use a platform-provided rule to ValidateEmailAddress.
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-167254 · Issue 651529
Reports database configuration documentation updated
Resolved in Pega Version 8.4.6
Documentation for working with the reports database has been updated to clarify that only a separate database with same schema/table names is supported. The complete information is available in the support documentation under Reporting Capabilities -> Reporting -> Creating advanced reports -> Setting up reports database.