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.

Split schema systems require additional privileges

Valid from Pega Version 7.1.2

On Oracle split schema systems, add the following database privileges:

  • Grant DROP ANY INDEX to the Admin User.
  • Grant UNLIMITED TABLESPACE to the Rules User.

Use the Oracle Enterprise Manager to add these privileges or refer to the 7.1.3 Upgrade and Installation guides for Oracle.

Existing collections are deprecated

Valid from Pega Version 7.1.7

The original implementation of the Collection form is deprecated. Legacy instances in your application remain functional; however, any new instance you create uses the redesigned Collection form. Use the Decision category in the Records Explorer to view all collections available to you.

For guidance on upgrade limitations, see the Deprecated Collection form.

Messages are rule resolved by class

Valid from Pega Version 7.1.7

As part of the Message form redesign, a class key part was introduced. While this key part is automatically handled as part of an upgrade or migration, it does change the available options you see in message SmartPrompts and how Rule-Message instances are rule resolved.

See Upgrade considerations for existing messages for more information.

Update Existing Applications wizard will run for every upgrade

Valid from Pega Version 7.1.7

The upgrade process from a PRPC 5.x or 6.x system to Pega 7.1.7 now automatically runs the Update Existing Applications wizard. This may extend the time that the upgrade process takes to complete, depending on the version you are upgrading from and the number of rules in your application.

Upgrading to Pega 7.1.7 with an Oracle database requires new role permissions

Valid from Pega Version 7.1.7

When upgrading or updating from a prior version to Pega 7.1.7, if your system uses an Oracle database, an additional role is required to support the Reversability functionality. In addition to the Oracle privileges specified in the Install Guides, the role SELECT_CATALOG_ROLE is required. Verify that this role is present before beginning the upgrade or update.

Add additional columns to customized work history tables

Valid from Pega Version 7.1.6

The standard work history table, pc_history_work, contains two new columns that return the latitude and longitude coordinate location of the action that prompted the history. Mobile devices can display this location as a street address. If you have a customized work history table, add these two columns to it:

  • <decimal name="pxLatitude" size="19" scale="9"/>
  • <decimal name="pxLongitude" size="19" scale="9"/>

Changes to archive.info in Pega 7.1.7

Valid from Pega Version 7.1.7

In Pega 7.1.7, the contents of the archive.info file have changed.

  • In versions Pega 7.1.6 and earlier, the archive.info file displays the build number of the Pega installation.
  • As of Pega 7.1.7, the build number no longer appears in the archive.info file.

In Pega 7.1.7, the archive.info file only displays a status message indicating whether or not the system is running, and the build number no longer appears. Instead, if the system is operational, the message “status=Running” displays in the archive.info file.

If there are any automated tests, scripts, or applications that rely on the archive.info file displaying the build number, those may fail and produce an error. It is recommended that any automation that relies on the build number displaying in the archive.info file be changed to look for the “status=Running” message.

Action required by admins for improved search

Valid from Pega Version 7.1.7

Starting November 13, 2014, after updating to or upgrading from a prior version to Pega 7.1.7, your system administrator must manually build all indexes for Elasticsearch before the system can automatically switch from Lucene to Elasticsearch.

It is recommended that you begin this manual re-indexing process for all enabled index types as soon as your update or upgrade is complete. The search landing page refers to Elasticsearch settings; during re-indexing, however, Lucene search continues to function to ensure that there is no interruption in search functions. When planning the re-indexing, be aware that the initial re-indexing requires significant resources on the host node and can be a lengthy process, depending on the number of rules and work objects in your system.

See the Pega 7.1.7 Upgrade Guide for information about manually indexing Elasticsearch.

Updates no longer require redeploying the prweb.war file or the application server-specific EAR file

Valid from Pega Version 7.1.7

Updating from Pega 7.1.7 to later versions of Pega 7 no longer requires that you redeploy the prweb.war file or the application server-specific EAR file.

Note that upgrades from versions prior to Pega 7.1.7 still require that you redeploy these files.

Service responses in HTTP and REST connectors are no longer modified

Valid from Pega Version 7.1.7

The Pega 7.1.8 release correctly leaves form service responses for HTTP and REST connectors unmodified. Upgrade to this release if you experience a problem in Pega 7.1.7 where service responses for HTTP and REST connectors are modified when the declared type in the Content-Type header is application/x-www-form-urlencoded. In this case, the responses were modified to a base 64 representation of the bytes in the string. In Pega 7.1.8, responses of type application/x-www-form-urlencoded are mapped to the property designated on the Connector record.

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