Published Release Notes

Improved capability to attach content in offline-enabled applications

The feature for attaching content in applications while in offline mode has been enhanced. A list of attached content is displayed in the application while in offline mode. You can view or delete attachments if the application has not yet been synchronized with the server. You also can change the maximum size of a file that you can attach while working in offline mode. This option gives you the flexibility to select the right size of attachment for a specific application for performance, memory limitation, or security reasons.

For more information, see Attach content support in offline mode.

Logging service now uses Apache Log4j 2

The Pega^® Platform now uses the Apache Log4j 2 logging service. Apache Log4j 2 improves performance and provides support for all log file appender types. As a result of this upgrade, the prlogging.xml file has been renamed to prlog4j2.xml and the format of the file has changed considerably.

For details about the new file format see Pega Platform logging with the Log4j 2 logging service.

For new installations or for upgrades to systems that were using the default logging configuration, no changes are needed. For information about updating custom log files after upgrading, see Customizations to the prlogging.xml file must be manually ported after upgrade. For information about updating your socket server if you use remote logging, see Socket server has changed for remote logging. For information about updated the web.xml file after upgrading, see Log file description in web.xml incorrect after upgrade to Apache Log4j2.

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

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

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.

Fingerprint authentication in Pega Mobile Client

The authentication feature in Pega Mobile Client has been extended to support user credentials that are secured by a fingerprint reader. The FingerprintAuthenticator object and its methods replace the TouchID API. A compatibility layer has been created to support custom mobile apps that use the deprecated API. This functionality is available on iOS and selected Android devices.

For more information, see Authentication API.

Enhancement to the error and warning handling JavaScript API

During offline post processing of a flow in an application, you can now use the ClientCache JavaScript API to handle informational and warning messages in addition to error messages. Several ClientCache API JavaScript functions have been updated for this purpose. Informational, warning, and error messages are displayed when you submit a form, but only error messages prevent you from advancing the case.

For more information, refer to Error and warning handling API in offline mode.

New customization options for paused custom mobile apps on Android

You can now customize the presentation of a paused custom mobile app for Android. You can upload a custom status bar icon and customize the title and message that are displayed in the device's notification area. Also, you can use a new optional parameter of the startKeepAlive method of the Pega Mobile Client's Container API as an alternative way of setting the notification title.

For more information, see Customizing the paused Android app notification.

Automatically process cases with SharePoint

You can now use Microsoft SharePoint Online to store and source case and Pulse attachments and to store and source attachments during automated case processing. Users only have to provide authentication and authorization details the first time they access SharePoint Online or when the trust has expired. The authentication profile must be OAuth 2.0 with a grant type of authorization code. The SharePoint Online component can be downloaded from Pega Exchange. For more information, see Downloading and configuring pluggable content management components.

Ability to set default values when importing data

You can now set default values for data that you import for a data type from a .csv file. By setting defaults, you can ensure that even when the .csv file data is incomplete, all of the data is imported. In addition, you can set default values for custom fields that do not have a matching source column in the .csv file. This feature is available for the Add and update and Add only import options. For mapped fields, the default value is used for new records if the source field is blank, and for existing records if both the source and target fields are blank. For custom fields, the default value is used for new records if a default value is provided, and for existing records only if the target field is blank.

For more information, see Importing data for a data type.

Support for round icons in Android 7.1 mobile apps

To improve the look and feel of Android mobile apps, round icons are now supported in apps that are created for Android 7.1. You can add the icons to the assets.zip file during the customization stage when you build the app in the Pega^® Platform.

For more information, see Branding mobile apps.