SR-B86779 · Issue 340677
Dirty state check added to TabbedScreenFlow data import
Resolved in Pega Version 7.4
In Data Import Wizard, selecting a file to import and then clicking cancel produces the prompt "You are about to discard your changes". After that, clicking Cancel and then Next caused the data wizard screen to vanish and the activity status message screen appeared. This was due to a missing dirty state check for the import harness pzTabbedScreenFlow7, and has been fixed.
SR-B87348 · Issue 334834
Deployment guides updated for Tomcat 7.3.1
Resolved in Pega Version 7.4
The deployment guides have been updated to reflect that Tomcat 7.3.1 has dropped the explicit reference to the urandom syntax that had been added in version 7.3.
SR-B89463 · Issue 338119
Upgrade error message enhancement
Resolved in Pega Version 7.4
An enhancement has been added to the upgrade process to give a more robust error message that can be used to help determine which parameter error needs to be corrected.
SR-B90072 · Issue 343826
global/ServiceExport directory created after restart
Resolved in Pega Version 7.4
The global/ServiceExport directory was not created after restart due to an error in the refactoring static content logic for MultiTenancy. As part of correcting this, the system will initialize the static content directories at a later point and not during the initialization of static content class.
SR-B91026 · Issue 338537
Update Guide documentation errors fixed
Resolved in Pega Version 7.4
The Update Guide documentation has been updated to correct two errors; 1) page 11 now correctly indicates that updates are available for Pega v7.1.0 and higher. 2) page 58 now correctly indicates the parameter name is 'upgrade' in the instruction "Type generateddl.bat or generateddl.sh and pass in the required --action argument #generateddl.bat --action upgrade"
SR-B92155 · Issue 345201
ConditionsUtils library present after migration
Resolved in Pega Version 7.4
The ConditionsUtils functions were failing to compile after migration. This was traced to the ConditionsUtils library not having been included in the migration, and has been corrected.
SR-B95350 · Issue 341577
Rollbacks use CreateDateTime for ordering list
Resolved in Pega Version 7.4
When processing a rollback for multiple hotfixes, the system was retrieving a list of uncommitted hotfixes from the database without specifying any order and, as a result sometimes the item were in the correct (i.e. reverse of installed) order and sometimes not. This was the unintended consequence of switching to using generated unique IDs which do not maintain any ordering, and has been fixed by modifying the process of retrieving the uncommitted hotfixes list to provide descending ordering based on pxCreateDateTime.
SR-C4008 · Issue 346439
Tile-generator updated to v1.8
Resolved in Pega Version 7.4
Tile-generator has been updated to version 1.8. This includes support for multiple subnets.
SR-C6074 · Issue 349037
Indexing doc clarifies JVM setting ramifications
Resolved in Pega Version 7.4
The Indexing section of the install / upgrade guides recommended setting the -Dindex.directory JVM argument, but did not explain the consequences of not doing so. The help document and PDN have now been updated to clarify that if this setting is not used and if a custom index file directory is used on the Search Settings Landing page, the system will revert to using the default directory if no other index host nodes are online when a server starts.
SR-C6941 · Issue 343726
Rollback information collection optimization
Resolved in Pega Version 7.4
During rollback information collection, a rule inventory is regenerated. This checking can include searching for instances that no longer exist in the database, potentially causing performance issues. In order to optimize the function and reduce unneeded logging, the rollback information collection process has been updated to reuse the rule inventory.