Published Release Notes

Tracer supports SOAP messages

You can now select a Tracer Settings option to display SOAP connector and services messages in Tracer, which provides users with a better understanding of SOAP connector behavior.

Actionable error message in integration wizards

Improvements have been made to the integration wizards for SOAP, SAP, and .NET that enhance the user experience by providing clearer, actionable error messages when there are problems with WSDL uploads; letting you edit the endpoint while creating or testing the integration; clarifying how the data source class layer is reused and removing confusing terms; and adding an option in Tracer to view SOAP messages generated or received by integrations.

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.

Support for large case attachments

You can now attach large files to a case on a variety of cloud storage options, including Pega Cloud File Storage, Amazon S3, Microsoft Azure, and JFrog Artifactory. Files can be 1 to 2 GB depending on your environment configuration. Attachments are streamed to the selected storage option without being loaded into memory, which reduces the risk of generating an out-of-memory error. Additionally, all cloud instances now have the new Pega Cloud File Storage repository defined.

For more information, see Storing case attachments outside the Pega Platform database.