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.

Geolocation tracking for the latest mobile client

Valid from Pega Version 8

The latest version of Pega Mobile Client™ now supports geolocation tracking for offline-enabled mobile apps. You can enable constant tracking when users work on specific cases from their worklists. This enhancement helps audit the trail of the case and increase the efficiency of your mobile users. For example, dispatchers at headquarters can track the routes of field workers and more effectively assign them tasks based on their current location.

For more information, see Tracking mobile users based on geolocation data.

Change logic does not work in Report Editor

Valid from Pega Version 7.1.2

The Report Editor​ change logic button does not work. As a workaround, use the rule form to change the logic.

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.

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.

New property pxCommitDateTime

Valid from Pega Version 7.1.8

A new property, pxCommitDateTime, records the time when a record or updated rule was committed to the database. This property also allows for incremental extracts when running BIX.

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.

JavaMail API upgrade has potential SMTP configuration error

Valid from Pega Version 7.1.8

The JavaMail API has been upgraded from 1.4.1 to 1.5.2 in this release. This improvement provides greater compatibility and secure connectivity with leading industry email servers.

During the upgrade process, there is a known issue for some configurations of email servers, including Microsoft Exchange Server, that requires the use of an additional setting. After upgrading to this release, if you experience authentication failures when attempting to send email or test SMTP connectivity, do one of the following:

  • Recommended: Review the Microsoft Exchange email server settings to ensure proper configuration for SMTP authentication. In some cases, the use of port 587 instead of the traditional default SMTP port 25 has been shown to address this issue.
  • Create the following Dynamic System Setting with the value "true," and then restart email listeners:

Owning Ruleset: Pega-IntegrationEngine

Setting Purpose: javamail/NoAuthMechanismsRetry

After any email server configuration or upgrade, it is recommended that email listeners are re-tested without using this Dynamic System Setting.

See About Email Account data instances for information on configuring email account 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