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-177323 · Issue 672422
Search string wildcard use documentation updated
Resolved in Pega Version 8.6.3
The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string.
INC-190130 · Issue 678542
Help information updated for using Elastic Search with Report Definition
Resolved in Pega Version 8.6.3
The support article "Configuring a report definition to run against an Elasticsearch index" has been updated to clarify that the search can pass multiple values with a space in pySearchString as it does OR operation on all the fields, and that filters in the report definition will be used when executing the report directly or when calling the report in the pxRetrieveSearchData activity.