REST APIs for VTable cache management and quiesce operations
Valid from Pega Version 7.4
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.
getRuleMessage APIs no longer prepend asterisks
Valid from Pega Version 7.4
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 > .
Internal rules in search results and explorers
Valid from Pega Version 7.4
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.
CRM core data types included in Pega Platform
Valid from Pega Version 7.4
Customer Relationship Management (CRM) core data types are now included with Pega® Platform, making it easier to bring your data into your Pega application. You can either import your data into the data tables for the CRM data types or use integration to communicate with your own system of record. The database tables for these data types are non-Pega formatted, which gives you better performance and more control over your data.
For information about the database tables, see CRM data types in Pega Platform.
Applications not working as expected when using fast processing for Connect REST and Service REST integration
Valid from Pega Version 7.4
In Pega® Platform 7.3.1, the Use fast processing option on Connect REST and Service REST rule forms did not work. The functionality has been fixed for Pega 7.4; however, some data model guidelines must be followed. If you use this option in Pega 7.3.1, and you did not follow the guidelines, your application might not work as expected after upgrading. Use the following data model guidelines when using fast processing:
- The JSON property names and the clipboard property names must match.
- The JSON tree structure and the clipboard tree structure must be similar.
- The scalar arrays in JSON must be mapped to the clipboard as page lists.
- Multi-dimensional arrays must be mapped into page lists of page lists with the same embedded property names.
In addition, page groups, value groups, and Java objects are not supported by fast processing.
Aggregating and browsing Visual Business Director data set
Valid from Pega Version 7.4
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.