SR-A19652 · Issue 246778
BIX filter failure alert added
Resolved in Pega Version 7.2.1
A warning has been added to issue an alert when filters are not being added while generating a BIX query.
SR-A19704 · Issue 234771
Refresh list action retains focus on work area
Resolved in Pega Version 7.2.1
When used as used as part of enabling successive rows, the refresh list action was returning focus back to first item rather than holding focus at the working point. This was found to be caused by a ?Select first row on initial load? option when ?Refresh List? is performed, and this code will no longer be called in this scenario.
SR-A19761 · Issue 237073
Fixed Require flag usage for Validate rule
Resolved in Pega Version 7.2.1
Saving a Validate rule that had a Required flag on one or more properties automatically reset the value, resulting in the inability to set the Required flag on any property of the rule. This was an error in the temporary activity handling, and has been fixed.
SR-A19803 · Issue 248102
Scheduled report generation errors skip sending email
Resolved in Pega Version 7.2.1
When a scheduled report encountered a database error, a blank email was sent to the recipients each time it retried instead of the expected behavior of stopping the process and not sending the correspondence. The code has been modified to ensure the process will properly skip the rest of the steps if there is StepStatusFail in the report generation.
SR-A19986 · Issue 244104
getAppHashForApplication API updated
Resolved in Pega Version 7.2.1
When logged in from an end user portal, editing a decision table and clicking on the gear icon to add a function would show the Function's headers (Example, Activity, string, etc.), but the functions list would not be loaded. This was traced to a timeout resulting from having numerous functions running on the portal combined with a configuration that returned an unowned AppHash when calling a ruleset from the production layer rather than the application layer, and has been resolved by adding logic to write out the AppHash when the appInfo is created from opening the application.
SR-A20067 · Issue 243517
Fixed thread locking for authenticated SOAP
Resolved in Pega Version 7.2.1
Exception messages were being logged when the authenticated inbound SOAP service was called from a client application due to two threads simultaneously trying to load a data page at node level. The locking has been corrected to resolve this.
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-A20162 · Issue 238035
Added validation to check for Agents run every *blank* days
Resolved in Pega Version 7.2.1
When configuring a Rule-Agent-Queue instance, the Pattern can be specified as "Recurring", which opens an "Advanced" button. The modal window that opens for the Advanced button allows specifying the recurring pattern, and it's possible to specify that an agent executes Daily, Every X days. If the Every X days option was selected, it allowed leaving the number field blank. However, doing this generated an invalid delay time error after the agent ran. To avoid this, validation will be performed on this field to ensure that a value is entered. Additional changes were also made to not allow a blank value in the field, numberOfMonths, numberOfDays, and numberOfYears as well.
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.