SR-A13449 · Issue 222715
Passivation fixed for softphone pages
Resolved in Pega Version 7.2
If a softphone page idled for 4 hours, a requestor level page (ScreenPopControlPort) became empty and prevented the user from logging in again. This was caused by a passivation issue that led to the parent page not being correctly set upon reactivation, and has been fixed.
SR-A10527 · Issue 221023
Issue with unwanted additional PageList property row corrected
Resolved in Pega Version 7.2
An empty row was being created on a page list property used in a work-item due to a logic issue with the TrackSecurityChangesLogic activity. This has been corrected.
SR-A10527 · Issue 221549
Issue with unwanted additional PageList property row corrected
Resolved in Pega Version 7.2
An empty row was being created on a page list property used in a work-item due to a logic issue with the TrackSecurityChangesLogic activity. This has been corrected.
SR-A5351 · Issue 218740
Optimized Clipboard reference processing
Resolved in Pega Version 7.2
Enhancements have been made to optimize reference properties processing for the ClipboardPageImpl.expandAllIfUnexpandedReferenceProperties method.
SR-A5351 · Issue 216605
Optimized Clipboard reference processing
Resolved in Pega Version 7.2
Enhancements have been made to optimize reference properties processing for the ClipboardPageImpl.expandAllIfUnexpandedReferenceProperties method.
SR-A7513 · Issue 218791
Corrected timing of OnMessage firing on restart
Resolved in Pega Version 7.2
MDB Listeners that have been processing incoming messages successfully were becoming problematic when the JVM was restarted. At that time, PRJMSListener's onMessage() started to process JMS messages from the queue even when the PegaRULES engine had not successfully initialized, resulting in large numbers of repeating error messages in the log file. In order to resolve this, the PRJMSListener.java has been updated to check the node initialization in OnMessage() itself instead of invoke() of JMSListenerServant.
SR-A6621 · Issue 221216
Fixed locking on node level declare pages
Resolved in Pega Version 7.2
In a scenario where data is being loaded from external system using an activity, the data page should be loaded only once for the first requester and all following requestors should refer to the loaded data page until it is expired. However, when multiple users accessed the data page simultaneously, the data page was being loaded for each one. This was traced to a timing issue with locking, and ReadOnlyDataPageHandler->loadDataPage() has been updated to insure node level data pages do the 'put' operation before releasing a lock.
SR-A4310 · Issue 212995
Fixed locking on node level declare pages
Resolved in Pega Version 7.2
In a scenario where data is being loaded from external system using an activity, the data page should be loaded only once for the first requester and all following requestors should refer to the loaded data page until it is expired. However, when multiple users accessed the data page simultaneously, the data page was being loaded for each one. This was traced to a timing issue with locking, and ReadOnlyDataPageHandler->loadDataPage() has been updated to insure node level data pages do the 'put' operation before releasing a lock.
SR-A10662 · Issue 220678
NVARCHAR2 support added for Oracle
Resolved in Pega Version 7.2
NVARCHAR2 support has been added for Oracle to handle Japanese and other special characters in Report Definition columns.
SR-A392 · Issue 204598
Updated SQLgenerator to avoid creating unneeded implicit DBs
Resolved in Pega Version 7.2
There is a known bug with Oracle JDBC drivers with handling synonyms when using getMetaData to get the database table details. For 7.1 installations/upgrades to split schema, if the customer has synonyms on the database for totally unrelated PRPC schemas it can cause issues with the upgrade. There were various ways to work around the issues (creating private synonyms for all of the tables in the new schema, upgrading to a single schema and then splitting, etc.) but to ease this process the system's SQLGenerator now has a check for zOS specific logic in order to ensure the generic table creation ddl will not be generated when it's not needed, as this was causing unnecessary implicit databases to be created.