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.

Aggregating and browsing Visual Business Director data set

Valid from Pega Version 7.4

Visual Business Director (VBD) data set has been enhanced to support the Aggregate and Browse operations. Aggregating aids testing your data in Pega® Visual Business Director. Browsing the content of the Visual Business Director data set provides transparency and helps to troubleshoot issues that are related to Pega Visual Business Director. You can use the new operations from the DataSet-Execute method or by clicking Actions > Run in the Visual Business Director data set form.

For more information see Creating a Visual Business Director data set record and Configuring the DataSet-Execute method for Visual Business Director.

getRuleMessage APIs no longer prepend asterisks

Valid from Pega Version 7.4

The Public APIs getRuleMessage(String aMsgDescr) and getRuleMessage(String aMsgDescr,String messageClass) no longer prepend asterisks ("**") to the message description when they fail to find a Rule-Message instance whose name matches the input message description. For information about these APIs, access the Public API documentation in Designer Studio by clicking Resources > Engine API.

Support for large case attachments

Valid from Pega Version 7.4

You can now attach large files to a case on a variety of cloud storage options, including Pega Cloud File Storage, Amazon S3, Microsoft Azure, and JFrog Artifactory. Files can be 1 to 2 GB depending on your environment configuration. Attachments are streamed to the selected storage option without being loaded into memory, which reduces the risk of generating an out-of-memory error. Additionally, all cloud instances now have the new Pega Cloud File Storage repository defined.

For more information, see Storing case attachments outside the Pega Platform database.

Data pages can source information from a robotic process automation

Valid from Pega Version 7.4

When you use robotic process automation (RPA), you can now configure data pages to source information from robotic automations so that you can connect your Pega® Platform application to legacy applications in your enterprise. By using automations to retrieve data and save it to a data page, you can use data virtualization to encapsulate your Pega Platform data model from the physical interface of a legacy system against which the automation is running.

For more information, see Obtaining information from robotic automations.

CRM core data types included in Pega Platform

Valid from Pega Version 7.4

Customer Relationship Management (CRM) core data types are now included with Pega® Platform, making it easier to bring your data into your Pega application. You can either import your data into the data tables for the CRM data types or use integration to communicate with your own system of record. The database tables for these data types are non-Pega formatted, which gives you better performance and more control over your data.

For information about the database tables, see CRM data types in Pega Platform.

Data pages can source information from a robotic desktop automation

Valid from Pega Version 8.1

You can now configure data pages to source information from robotic desktop automations (RDA). Using an RDA to source a data page allows you to connect your Pega Platform™ application to any application that is accessible from an end-user's desktop. By using automations to retrieve data and load it into a data page, you can use data virtualization to separate your Pega Platform data model from the physical interface of a legacy system against which the automation is running.

For more information, see Obtaining information from robotic automations.

Data and integration troubleshooting enhancements

Valid from Pega Version 8.3

Identify how data is loaded in user interface (UI) elements, discover the data sources used, and navigate to the relevant rules by using the new Live Data tool. Use the Live Data tool to quickly troubleshoot data and integrations by providing data page information or autopopulate properties from the UI without searching through the clipboard.

For more information, see Troubleshooting data in UI elements.

Retrieve a flat list of fields from Pega Digital Experience APIs

Valid from Pega Version 8.3

You can now use the flatListOfFields parameter to retrieve a list of the fields in a case or flow action. With this parameter, you avoid parsing all the layout information for the Pega Digital Experience API, making it easier for you to see only what you need to build your user interface.

The following Pega Digital Experience APIs support the flatListOfFields parameter:

  • GET /casetypes/{ID}
  • GET /assignments/{ID}/actions/{actionID}
  • GET /cases/{ID}/actions/{actionID}

For more information, see Retrieve a flat list of fields from Pega APIs.

Attachment migration from Pega database storage to a repository

Valid from Pega Version 8.3

You can now migrate case attachments from Pega database storage to a repository by using a wizard from Pega Platform™. This ability is useful, for example, when you migrate from an on-premises deployment to a Pega Cloud Services environment and you want to reduce the size of your Pega database and manage all your case attachments in a single location.

For more information, see Migrating case attachments to a repository.

Specify a queue of user operations in Pega Digital Experience APIs

Valid from Pega Version 8.3

You can now specify a queue of page instructions for user operations on embedded pages, page lists, and page groups in Pega Digital Experience APIs. The page instructions allow your client application to more accurately model users’ actions.

Pega Digital Experience APIs support the following operations:

  • For embedded pages: DELETE, REPLACE, and UPDATE.
  • For page lists: DELETE, REPLACE, UPDATE, APPEND, INSERT, and MOVE.
  • For page groups: DELETE, REPLACE, UPDATE, and ADD.

For more information, see Page-related operation queuing with page instructions in Pega APIs.

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