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.

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.

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.

Configuration required for data operations on external schema when using a Postgres database

Valid from Pega Version 7.1.8

When you use the API for data operations on external schema in the Postgres database, you must update the prconfig.xml file. No other platform requires a prconfig.xml update.

To update the prconfig.xml file:

  1. Stop the server and add the following entry to the prconfig.xml file:
    env name="database/databases/postgres_ext/defaultSchema"
    value="externalschema"
    where postgres_ext is the external database that uses the external schema “externalschema”.
  2. Restart the server.

Customizations to the prlogging.xml file must be manually ported after upgrade

Valid from Pega Version 7.3

As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, the name of the logging configuration file has changed from prlogging.xml to prlog4j2.xml and the format of the file has changed considerably. If you customized your prlogging.xml file, port the customizations to the new prlog4j2.xml file. If you do not port the changes, the Pega® Platform uses the default prlog4j2.xml file and disregards your customized prlogging.xml file.

For more information about customizing your log files, see the Apache Log4j 2 documentation.

Socket server has changed for remote logging

Valid from Pega Version 7.3

As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, the socket server that is used for remote logging has changed from the Log4j remote logging package with the LogFactor5 log analysis tool to TcpSocketServer. If you use remote logging, update your socket server to TcpSocketServer. For more information, see Installing and using remote logging.

Log file description in web.xml incorrect after upgrade to Apache Log4j 2

Valid from Pega Version 7.3

As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, it is recommended that you update the log file description in the web.xml file from location of prlogging.xml file to location of prlog4j2.xml file. The description indicates which log file is in use. Updating the description avoids confusion about which log file is current. Change the description as shown in the following example.

<resource-ref id="ResourceRef_5">
<description>location of prlog4j2.xml file</description>
<res-ref-name>url/pegarules.logging.configuration</res-ref-name>
<res-type>java.net.URL</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>

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