Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Easily configure the live and interactive map control

Valid from Pega Version 7.1.8

The AddressMap control has been enhanced with a text input field so that users can mark a location on a map.

For example, an insurance adjuster can indicate the location of the accident when filing a case. By selecting Allow marker repositioning to change address value and dragging the marker pin, the Text Input field is automatically updated.

Derby databases are no longer supported

Valid from Pega Version 7.1.8

Previously, an embedded Derby database could be used as a file system. This setup was configured by setting storage/class/<<filesystem>>/type to "embedded" in the prconfig file.

After upgrading, storage types that are specified as "embedded" now default to the local file system.

Quickly attach a file to a case directly on a user form

Valid from Pega Version 7.1.8

In form configuration, the Attachment field type allows users to attach files directly to the form rather than performing an additional action.

For example, an insurance adjuster can take a photo of a vehicle and add the photo directly to the form. When the field type is configured as an attachment, at run time a new section is auto-generated with an attachment control that includes a read-only text input field and a browse button.

Enhanced form configuration reuse

Valid from Pega Version 7.1.8

In Case Designer you can reuse existing form fields when configuring forms. You can browse a set of existing fields and add them to the form by clicking an icon or by dragging and dropping. You can drill down through field levels to add embedded field levels. Fields are also searchable.

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.

Quickly preview laptop, tablet, and phone views for Case Manager portals

Valid from Pega Version 7.1.8

You can use the Mobile preview item from the Operator menu to rapidly preview how the current portal is displayed in the default browser window size on laptops, tablets, and phones. You can view either portrait or landscape orientations for both tablets and phones. Because you do not need to use actual devices for testing, development is faster and easier.

For more information, see Mobile browser preview for laptops, tablets, and phones.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us