Custom properties can be passed to an Oracle database
Valid from Pega Version 7.2
You can pass a customizable set of property values to an Oracle database when a connection is established so that an SQL statement can be run. This feature provides the ability to implement object-level security for data access from a Pega 7 Platform application by defining Virtual Private Databases (VPDs) on class tables that reference the information passed. For example, you could pass in an operator's branch office into the context of every query run against the Oracle database to ensure that the operator has access only to data that is applicable to the operator's branch.
This feature is available only for Oracle databases and for a Data-Admin-DB-Name instance that is not PegaRULES or PegaDATA, and has the same connection metadata (JNDI, URL) as PegaData.
See Passing custom properties to an Oracle database.
Pega 7 Platform supports X-Forwarded-* (XF*) HTTP headers
Valid from Pega Version 7.2
When deployed behind a load balancer, the Pega 7 Platform can formulate absolute URLs while responding to requests, without any additional configuration. The load balancer must be configured to use XF* headers. Consequently, the configuration property contextrewriteenabled is deprecated.
Improved application performance when responding to SOAP requests
Valid from Pega Version 7.2
When an application serves multiple requests, the contention placed on the ContextHash class is reduced because all threads can concurrently access the mHash instance variable, which improves performance. To experience this benefit, redeploy the prweb.war file for web tier deployment or redeploy the prpc_wls_jee4.ear file for e-tier deployment.
Stage-based revision and change request management enhancements
Valid from Pega Version 7.2
The revision and change request processes are based on the case management capabilities provided by the Pega 7 Platform. The customizable flows that controlled the behavior of the revision and change request management (pyManageRevision, pyManageChangeSet, pyApproveChangeSet, and pyDirectDeployment) are now part of the Revision and Change Request case types that govern the behavior of revision management. The change from flow-based to stage-based revision management makes the process more transparent and easier to modify.
For more information, see Stage-based revision and change request management.
Help now available for the Predictive Analytics Director (PAD) portal
Valid from Pega Version 7.2
Help topics for Predictive Analytics Director (PAD) are now available. The comprehensive PAD documentation helps you to understand how to develop and create predictive models that you can combine with other components in Decision Strategy Manager (DSM).
For more information, see Predictive Analytics Director (PAD) and Improvements to the Predictive Analytics Director (PAD) portal.
Enhanced performance of autopopulated properties
Valid from Pega Version 7.2
You can improve performance when accessing data from autopopulated properties that are defined by keys or parameters. If the properties were created in an earlier version of the product, run the pzReSaveAutoPopulateProperties activity to gain a performance improvement.
For more information, see Enhancing performance when loading autopopulated properties.
Pega 7 Platform startup fails with an evaluateWhen-Exception after upgrade
Valid from Pega Version Pega Platform
If the batch requestor, Data-Admin-Requestor.BATCH, does not have access to the PRPC:Agent access group, the Pega 7 Platform fails to start up after an upgrade. The checkSecurity step fails with an evaluateWhen-Exception while evaluating access to the Data-Admin-System-Settings.pzSharedTenant when rule.
To resolve this issue, follow these steps:
- On the pre-upgraded environment, grant the Data-Admin-Requestor.BATCH access to the PRPC:Agents access group. See the online help for information about granting access to access groups.
- Move the database table record that corresponds to the batch requestor type from the pr_data_admin table of the pre-upgraded environment to the pr_data_admin table on the upgraded environment. See the online help for information about moving database table records.
Column Populator utility documentation out of date for prior versions
Valid from Pega Version 7.2
The documentation for using the Column Populator utility to populate newly exposed database columns is out of date for Pega 7 Platform versions prior to 7.2. For all Pega 7 versions, refer to the Pega 7.2 help documentation for instructions about how to use this utility.
Improvements to Visual Business Director (VBD)
Valid from Pega Version 7.2
Business monitoring and reporting no longer depends on the external Visual Business Director service because VBD is now embedded in the Pega 7 Platform. You add a VBD node to the cluster to access VBD for simulations and monitoring. In addition, when you use the Google Chrome browser, VBD launches as a new HTML client that provides the visualization.
For more information, see The Visual Business Director (VBD) HTML client and Accessing Visual Business Director (VBD).
New Proposition Filter rule
Valid from Pega Version 7.2
Instances of the Proposition Filter rule allow you to define the validity, eligibility, and relevancy criteria for a set of strategy results. Proposition Filter rules improve performance of filtering propositions that are based on proposition data and customer properties. Proposition filters give more testing and debugging capabilities by offering explanation properties. They are referenced in strategies through the Filter component.
For more information, see About Proposition Filter rules and Strategy components - Arbitration.