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.

Automate business process tracking by importing Excel files

Valid from Pega Version 8.5

To track business processes status and data, you can now import Excel files when you create a case or data object in App Studio. This functionality provides the following enhancements:

  • You can now upload a CSV file when you create a case or data object in App Studio. By importing a CSV file, you can use the data in your spreadsheet to define your data model.
  • You can generate a data import template that you can use to import a file in its original format during production.
  • You can upload .xlsx files to avoid resaving your Excel file as a CSV file.

For more information, see Creating a data model from a spreadsheet.

Data APIs support data exploration in React UI tables

Valid from Pega Version 8.5

Data APIs have been enhanced to support filtering, sorting, paging, and aggregation in React UI tables. You can use that functionality to access your data quickly and intuitively. For example, by using paging, you can query a data page to retrieve the second page of an employee contact list and specify the number of results that are displayed on the page.

For more information, see Data API performance and limitations.

Support for application-specific REST API calls

Valid from Pega Version 8.5

You can now call an authenticated REST API in the context of any application that is listed on an operator record by using the application alias URL. With the application alias URL, you can also develop REST services without changing the access group in the service package. REST services run in the context of the access group that points to the provided application, instead of the access group that is specified in the service package.

For more information, see Invoking a REST service rule.

Savable data pages support loading pages individually from a page list

Valid from Pega Version 8.5

You can now load individual pages in a page list from single object data pages to your case and data types. This functionality allows you to save autopopulated properties with the Load each page individually option using a flow action, save data page smart shape, or the activity method.

For more information, see Saving data in a data page as part of a flow.

Word merge support with Microsoft Silverlight plug-in

Valid from Pega Version 7.1.3

PRPC features that integrate with the Word merge capability are now cross-browser. ActiveX controls (which are only compatible with IE) have been replaced with Microsoft Silverlight. This plug-in must be downloaded separately from Microsoft, as it is not shipped with PRPC.

Some common PRPC features affected by this change include the Application Document Wizard, App Profile, Specifications Landing Page, Specification form, and Case Type Landing Page.

Prior to using these features, Users of PRPC 7.1.3 need to set up their client system(s) as follows:

1. Install Silverlight plug-in

Follow the PRPC prompt to install Silverlight when you attempt to use the Word merge feature:

Silverlight1.jpg

Or download package directly: www.microsoft.com/silverlight/

2. Install PRPC prerequisites

Microsoft Internet Explorer (IE) browsers automatically detect the need for PRPC prerequisites and will prompt for install:

Silverlight2.jpg

Non-IE browsers will load a pop-up window when the user attempts to use the Word merge feature.  Use the link to manually download PRPC prerequisites:

Silverlight3.jpg

Extract the .zip file, execute setup.exe and follow the install wizard:

Silverlight4.jpg

Administrators setting up multiple clients at once may refer to the pzSLpreReqs.cab available in the PRPC 7.1.3 resource kit.

3. Restart browser

Log out of PRPC, close all open sessions and restart your browser.

The PRPC feature integrated with Word merge is now ready for use; Silverlight prompts are no longer displayed.

4. Troubleshooting

Silverlight installation requires access to your file system and a registry setting update to “trust” the associated Verisign certificate.  Contact your administrator if you encounter any security or permission errors during this process.

While Silverlight is cross-browser, it is not fully cross-platform.  Mac users may use Word merge features in Chrome via Parallels.

See the PRPC Developer Help for more information on browser setup requirements.

Logging service now uses Apache Log4j 2

Valid from Pega Version 7.3

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.

Automatically process cases with SharePoint

Valid from Pega Version 7.3

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

Valid from Pega Version 7.3

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.

Ability to persist request data for synchronous REST Service failures

Valid from Pega Version 7.3

Request data can now be persisted when synchronous REST Service processing fails. To ensure that data is not lost and can be reprocessed, set the Execution Mode on the rule form to Execute synchronously (queue on error).

For more information see Service REST form - Completing the Service tab.

Create pluggable web storage components for case and Pulse attachments

Valid from Pega Version 7.3

You can now implement and post your own pluggable web storage components for use with case and Pulse attachments. These web components can be plugged in to Pega® Platform without the need to make changes to Pega Platform itself. The ability to create a pluggable web storage component is useful when you want to use a web storage provider that does not have an existing pluggable web storage component.

For more information, see Guidelines for creating pluggable components for storing and sourcing case and Pulse attachments.

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