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-A19705 · Issue 246975
Hash table logic fixed for invokeMQConnector
Resolved in Pega Version 7.2.1
Logic issues were found and fixed related to hashtable usage for invokeMQConnector.
SR-A19761 · Issue 237142
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-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-A19782 · Issue 237144
Mandatory date and amount fields validation performed before reset
Resolved in Pega Version 7.2.1
Date and amount fields changed to incorrect format if any mandatory field was empty and screen was saved. This was traced to a handling error where the reset of read-only formatting happened before the validation check, 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-A19810 · Issue 239496
PopulateRecipient set to consider pyEmail1
Resolved in Pega Version 7.2.1
After upgrade, an error was occurring while trying to save the Data-Corr-Email.populateRecipient activity into an application ruleset due to code changes used to specify the email property field. The "populateRecipients" activity has fallback logic to handle using pyEmailAddress [old method] for pyAddresses(Email) [new method], but some sites had the data in ".pyEmail1". PopulateRecipients has now been updated to look for pyAddresses(Email)").(".pyEmailAddress") and then consider values from ".pyEmail1".
SR-A19811 · Issue 241385
Enhanced column supports in 'Export to Excel'
Resolved in Pega Version 7.2.1
Reports using functions in columns were not working with 'Export to Excel'. This has been fixed. Support has also been added to display all the report column localized values in pzListViewExcelData while doing Export to Excel: Simple Column, Joins, Declare Index, Associations, Sub Report, Functions and Embedded Properties.
SR-A19811 · Issue 239285
Enhanced column supports in 'Export to Excel'
Resolved in Pega Version 7.2.1
Reports using functions in columns were not working with 'Export to Excel'. This has been fixed. Support has also been added to display all the report column localized values in pzListViewExcelData while doing Export to Excel: Simple Column, Joins, Declare Index, Associations, Sub Report, Functions and Embedded Properties.
SR-A19814 · Issue 237605
Entropy pool explicitly coded for UNIX/Linux Oracle installations
Resolved in Pega Version 7.2.1
When running a new install on an Oracle database in a UNIX environment, install was failing repeatedly at the same point when attempting to import one of the application bundle components. This issue was traced to the way the newer versions of the Oracle JDBC driver gather entropy by defaulting to the use of /dev/random. When running in an environment where there this is not a lot of noise, the entropy pool will eventually be empty and the connection will be reset. Earlier versions of the Oracle JDBC driver did not see this issue. To resolve this, in the event that a deployment is being performed on a UNIX/Linux platform using an Oracle database, the -Djava.security.egd=file:///dev/urandom will be specified whenever a java utility is started.