Simplified process for JMS MDB listener deployment
Valid from Pega Version 7.1.8
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
Valid from Pega Version 7.1.8
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
Valid from Pega Version 7.1.8
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
Valid from Pega Version 7.1.8
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
Valid from Pega Version 7.1.8
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
Valid from Pega Version 7.1.8
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.