Support for reserved keywords in database column names
Valid from Pega Version 7.2.1
Databases use reserved keywords such as Group, Order, Rank, and Date to define and manipulate data. The list of reserved keywords is specific to each database. Column names can now include reserved keywords.
High number of busy waits when using Oracle SecureFiles
Valid from Pega Version 7.2.1
You might experience a high number of buffer busy waits when using Oracle SecureFiles for BLOB storage. An Oracle buffer busy wait occurs when a session cannot access a database block in the buffer cache, because another session is either reading the block into the buffer or changing the buffer. As a best practice, use Oracle 11.2.0.4 or later, because earlier versions have more problems with SecureFiles. In addition, to minimize the number of busy waits, set the hidden Oracle parameter _securefiles_concurrency_estimate to 50, and partition the table by using a composite range hash partition that is based on the pxCreateDateTime and pzInskey columns.
For more information, see Troubleshooting: High number of busy waits when using Oracle SecureFiles.
View and apply schema changes when upgrading or updating
Valid from Pega Version 7.2.1
When you upgrade or update, you can view the schema changes to the default work and history tables and apply the changes to your cloned tables. By applying the changes, you improve performance and can take advantage of the latest reports on those tables.
For information about viewing and applying schema changes as part of the upgrade or update, see the Pega 7 Platform Upgrade Guide or the Pega 7 Platform Update Guide.
For information about using the Designer Studio tool or the command-line tool, see Updating cloned tables after an upgrade or update.
Discontinued support for multithreaded requestors
Valid from Pega Version 7.2.1
Multithreaded requestors are no longer supported in the Pega 7 Platform. Multithreading was previously specified by the prconfig setting initialization/allowMultiplePRThreads. If this setting is set to true when you upgrade to Pega 7.2.1, errors occur during the quiesce process.
Support for data rollback and commit in service-enabled system management
Valid from Pega Version 7.2.1
You can use the service-enabled manage tracked data tool to roll back or commit data that has been imported with the service-enabled import tool.
The service-enabled manage tracked data tool lets you commit imported data or roll back all non-committed data instances to their state immediately prior to when they were imported. The tool only tracks and supports rolling back data instances that do not belong to the PegaRULES database name (Data-Admin-DB-Name).
For more information, see Rolling back and committing tracked data.
Child case queries can be slow after upgrade
Valid from Pega Version 7.2.1
After upgrading, performance might be slow when you run queries on child cases for work tables that existed prior to the upgrade. This issue is often indicated by PEGA0005 (query time exceeded limit) alerts that can be correlated to these queries in the logs. To resolve the issue, add a database index to each of your work tables by using a multicolumn index on the pxCoverInsKey, pxObjClass, and pyStatusWork columns.
For more information, see Performance improvements for child case queries.
Improved engine startup times
Valid from Pega Version 7.2.1
Performance enhancements in this release decrease engine startup times for new Java virtual machines (JVMs) and improve rule assembly for libraries. JVM startup times are faster because rule utility libraries and functions are no longer generated at startup. For more information, see Extract marker file not created at startup.
Extract marker file not created at startup
Valid from Pega Version 7.2.1
The extract marker file (PegaRULES_Extract_Marker.txt) is not created at startup, because the rule utility libraries no longer need it. If you used to use the extract marker file to clear the static content file-based cache, to look up lists, or to control starting activities with web nodes, you can delete the contents of the PegaRULES temporary directory instead.
Batch database processing improvements
Valid from Pega Version 7.3
Batch database processing has been enhanced to ensure that a constraint violation does not occur when you save transactions to a table with a foreign key dependency. Because batch processing changes the order of save operations, it is disabled for transactions with foreign key dependencies. Disabling batch processing ensures that a record with a foreign key dependency on another record will not be written before the record on which it is dependent.
For more information about how batch database processing works and how to enable and disable it, see Batch processing during database write operations.
Improve cluster security by limiting concurrent operator sessions
Valid from Pega Version 7.3
You can increase the security of a Pega® Platform cluster by limiting the number of concurrent sessions allowed for each operator. Because operators typically do not require multiple concurrent sessions for performing their work, limiting the number of sessions reduces the chance that an unknown or untrusted person could access systems in the cluster. Use the new setting Number of concurrent sessions allowed for each operator on the Production tab of the System Data Instance form to configure the number of concurrent sessions for operators. You must restart your system when you change this setting. You can also create a list of operators by using the presence/maxsessions/operators/whitelist Dynamic System Setting, to which the maximum number of concurrent sessions setting will not apply.
For more information, see System form - Completing the Production tab.