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.
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.
Agents not running after update of EAR-based deployment
Valid from Pega Version 7.1.7
If you update an EAR-file deployment and your update meets both of the following criteria, you must redeploy the prpc_*.ear file for your application server after you complete the update to avoid agent-related errors:
- Updating from Pega 7.1.7, Pega 7.1.8, or Pega 7.1.9
- Updating to Pega 7.1.10, 7.1.11, 7.2, or 7.2.1
If you do not redeploy the prpc_*.ear file, you will see the agent-related issues that are described in the support article Agents are not running.
For information about redeploying, see the Pega 7 Platform Update Guide for your target version of the Pega 7 Platform.
Naming pattern changed for file data sets
Valid from Pega Version 8.6.3
File data sets are used to import from and export data to a file repository. In case of data export, prior to version 8.6.3, the first file exported had the same file name that was provided by the user in the data set, and any subsequent file exported to the repository had a unique identifier appended to it. Starting in Pega Platform version 8.6.3, each file has a unique identifier, automatically generated based on the data flow node, thread ID, and timestamp.
Upgrade impact
If your process to consume output files expects files with a specific name, it may not be able to process the resulting files correctly.
What steps are required to update the application to be compatible with this change?
If you have configured the process before updating to Pega Platform version 8.6.3, but the exported files are no longer recognized by downstream processing logic after the upgrade, ensure that the downstream tool is configured to recognize the files by a pattern rather than the full name. For example, when referring to files exported to the repository, use the * character to indicate a pattern instead of using the full file name. For example, use Export*.csv to refer to the files.