Enhanced date circumstancing option
Valid from Pega Version 7.2
The date range and as-of date circumstancing features have been merged into a single feature called date circumstancing. Accordingly, the new Property and Date circumstancing option provides more flexibility when you circumstance a rule. For more information, see Specializing a rule.
Renaming a system creates the required data requestors
Valid from Pega Version 7.2
When you rename a system, either from the System Name landing page or by updating the prconfig.xml file, any missing data requestors are automatically created by the Pega 7 Platform. The Data Admin System Setting is also created, if it is missing.
Case Manager option for searching only attachments
Valid from Pega Version 7.2
Case Manager search now has an option to search only case attachments. When you search attachments, a new column in the search results displays a paperclip icon with the number of attachments that match the search string. You can click the number to display a list of matching attachments for the selected case.
Configure Elasticsearch index nodes to ensure availability of index files
Valid from Pega Version 7.2
You can now configure Elasticsearch index host nodes in a Pega cluster outside of the Search landing page. This change ensures that search index files are always available by eliminating the need for manual configuration on the Search landing page. Use the new index.directory=<index_directory> command-line setting during JVM startup to indicate that this node is an index host node and to specify the directory where the index files will be hosted.
In addition, offline Elasticsearch index nodes can now be removed by using a new prpcUtils command-line option. For more information, see Managing Elasticsearch index host nodes outside of the Search landing page.
New Schema Tools and Query Inspector landing pages for Pega Cloud
Valid from Pega Version 7.2
Two landing pages have been added for advanced database administration tasks for Pega Cloud customers who use a Pega-hosted instance. These landing pages minimize the operations that need to be performed outside of the Pega 7 Platform. They are available only for customers who use a Postgres database.
From the new Schema Tools landing page, you can view PegaRULES and PegaDATA database schemas, increase the size of a column, add a composite or function index, update database statistics for a table, and defragment a table.
From the new Query Inspector landing page, you can enter an SQL query and generate an explain plan.
To use these landing pages, you must have the new PegaRULES:DatabaseAdministrator role. You access the landing pages by clicking or by clicking . The individual features that you can access are determined by the privileges that are assigned to you.
For more information, see Schema Tools and Query Inspector landing pages for tuning and maintaining databases in the Pega Cloud.
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.
The Declarative Network display is now cross-browser compatible
Valid from Pega Version 7.2
The Declarative Network display can now be displayed on all browsers.
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.
Label changes to field types in Case Designer
Valid from Pega Version 7.2
The following field types have been renamed in Case Designer to be consistent with Data Designer and other areas of the Pega 7 Platform.
| Label in previous versions | Label in Pega 7.2 |
|---|---|
| Text | Text (single line) |
| Text (multiple lines) | Text (paragraph) |
| Check box | Boolean |
| Date and time | Date & time |
| Date | Date only |
| Drop down | Picklist |
| Number (integer) | Integer |
| Number (decimal) | Decimal |
Users who upgrade from versions prior to Pega 7.2 do not have to take any action because the label changes are cosmetic and do not affect the underlying controls or property types that support form building.
For more information about the field types that you can use when building a form, see Storage and display of single-value fields.
New Pulse gadgets for developers
Valid from Pega Version 7.2
Pulse for the Pega 7 Platform provides two new gadgets: pxContextFeed and pxActivityFeed.
The pxContextFeed gadget is a section that you can integrate with your application. Users can use this gadget to communicate with other users by creating and sharing posts within a given context. You can also customize the gadget or build your own Pulse interface by using a number of APIs.
The pxActivityFeed gadget aggregates all the activity feeds for the cases that a user follows without requiring that individual cases for posts be viewed.
For more information, see the help topic Pulse gadgets and custom APIs.