Published Release Notes

Data validation before importing

Data imported into a data type is now validated before it is imported. Validating data before importing it ensures that the data is valid and reduces the amount of time required to manually analyze and validate your data.

For more information about importing data into a data type, see Importing data for a data type.

Enable different REST service rules for distinct resource URIs

You can now specify different service REST rules for distinct resource URIs. This functionality provides different processing options, request handling, and response handling for each distinct resource URI. Additionally, it eliminates the need to develop and maintain complex logic to handle all possible resource URI paths.

For more information, see Distinct URI specification for service REST rules.

Precision of Oracle Timestamp property when using RDB-Save

DateTime properties that are mapped to an Oracle Timestamp column will experience a loss of precision when they are saved using the RDB-Save method. When you use RDB-Save for an Oracle Timestamp, precision will be accurate to the second. For example, a value of 20171119T124745.006 will be saved as 20171119T124745. When you use Obj-Save, precision will be accurate to the millisecond. For more information, see DateTime property mapping in Oracle for Pega 7.

Internal rules in search results and explorers

Using old: is no longer supported in search. You can include internal rules in search results and make them available in the Application and Records explorers. Include internal rules in search results either by adding the PegaDevelopmentruleset to your application or by clicking the Enable diagnostic features option in your operator preferences.

REST APIs for VTable cache management and quiesce operations

You can access, control, and manage in-memory VTable in cache for a specific rule class and instance name by using new Nodes REST APIs. You can reassemble and reload rules across the cluster and obtain cache entries for a specific node in the cluster. You can also start and cancel the quiesce process on any node in the cluster by using either immediate drain or slow drain.

For more information, see Pega API for Pega Platform 7.4 and Pega API.

REST APIs for cache management and requestor pools management

You can manage various caches in Pega^® Platform, for example, the clean cache or the repopulate cache, or you can get cache statistics for the authenticated user by using the new Caches REST APIs. You can manage requestor pools, for example, clear a requestor pool, by using the new Pools REST APIs. These APIs allow external systems to consume and manage Pega resources.

The new REST APIs are for Conclusions Cache, Declarative Page Cache, Declarative Rules Cache, Rule Cache, Application-Based Assembly (ABA) Cache, and Requestor Pool Management.

For more information, see Pega API for Pega Platform 7.4 and Pega API.

REST APIs for viewing Pega Platform configuration settings

New REST APIs in the Nodes category provide a view of the current configuration settings for any node in a cluster or for an entire cluster. You can also find a specific node ID by listing all the nodes in the cluster. To diagnose settings issues for a node, you can download the prconfig.xml file.

For more information, see Pega API for Pega Platform 7.4, Pega API, and Viewing the current configuration settings for a node or the whole cluster.

Saving data without using an activity

You can now define data pages to persist data to a system of record. Savable data pages provide a simple way to save data pages without needing to configure an activity. List savable data pages on a flow action to provide users with the ability to update values and save the changes with a savable data page. Use a Save Data Page smart shape to save data as a part of case processing.

For more information, see Creating a data page to save data.

Aggregating and browsing Visual Business Director data set

Visual Business Director (VBD) data set has been enhanced to support the Aggregate and Browse operations. Aggregating aids testing your data in Pega^® Visual Business Director. Browsing the content of the Visual Business Director data set provides transparency and helps to troubleshoot issues that are related to Pega Visual Business Director. You can use the new operations from the DataSet-Execute method or by clicking Actions > Run in the Visual Business Director data set form.

For more information see Creating a Visual Business Director data set record and Configuring the DataSet-Execute method for Visual Business Director.

getRuleMessage APIs no longer prepend asterisks

The Public APIs getRuleMessage(String aMsgDescr) and getRuleMessage(String aMsgDescr,String messageClass) no longer prepend asterisks ("**") to the message description when they fail to find a Rule-Message instance whose name matches the input message description. For information about these APIs, access the Public API documentation in Designer Studio by clicking Resources > Engine API.