Published Release Notes

Simplified process for JMS MDB listener deployment

The process for deploying a JMS message-driven bean (MDB) that represents a JMS MDB listener has been streamlined for new enterprise applications. It is now less complicated and can be performed in fewer steps.

For more information on deploying to WebSphere, WebLogic, and JBoss, refer to the PDN article Deploying a JMS message-driven bean (MDB) that represents a JMS MDB listener in Pega 7.

Using SAML 2.0 for web single sign-on

Provide a seamless user-authentication experience across your SAML 2.0-enabled service provider applications by using SAML 2.0 for web single sign-on.

Pega uses this industry-standard protocol to ensure simple and proven connectivity with your Identity Provider (IdP). The Pega 7 platform is fully conformant with the SAML 2.0 web single sign-on and single logout profiles.

For additional information about SAML 2.0 conformance, including configuring Pega 7 as a service provider, see SAML 2.0 conformance for web single sign-on and single logout profiles.

FTPS added to FTP server

When using FTP Secure (FTPS) in an FTP Server record, you can securely transfer files by using TLS/SSL. A new Security section has been added to the Edit FTP Server configuration page for enabling and configuring FTPS.

For more information, see FTP Secure for FTP server records.

Enhanced error handling in data pages

All error details in data pages are captured in one easy-to-remember location on the data page. New functions for handling errors from the data layer without using a post-load activity allow you to handle errors without guardrail violations. A new template error handling transform helps to simplify error handling from your response data transforms.

For more information, see Data page error handling.

Pega Connect-CMIS support for NTLM authentication

Support is now available for using Connect-CMIS rules and NTLMv1 authentication with enterprise content management (ECM) systems such as Microsoft Sharepoint. This capability is provided by the underlying Apache Chemistry OpenCMIS libraries that impose the following restrictions:

• Only a single NTLM-enabled CMIS connector can be used per node (JVM).
• Only Basic Authentication and NTLMv1 are supported as authentication methods with Connect-CMIS.

Enhanced interoperability with enterprise content management products

The Content Management Interoperability service (CMIS) capabilities of the Pega 7 platform now provide enhanced interoperability with enterprise content management products. This improvement uses modern web services components that require a Pega platform running Java 7 or higher when CMIS connectivity through SOAP web services are utilized.

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.