circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

Published Release Notes

Find release notes for the selected Pega Version and Capability.

Browse resolved issues for Platform releases.

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.

Valid from Pega Version 8.1

The Supported artifacts check box has been removed from the repository rule form. Developers can use repositories to provide centralized storage, versioning, and metadata support for application artifacts.

For information about repository connections, see Creating a repository for file storage and knowledge management.

Valid from Pega Version 8.1

Support for the character data type for local variables in activities is deprecated. Use the string data type instead.

For more information about activities, see Activities.

Valid from Pega Version 8.1

In the rare case in which a step page context is null, or the pxObjClass associated with the step page is empty, the system no longer attempts to resolve the when rule against @baseclass. As a result, you might see more rule not found errors. Check the step page context and class and ensure that they are not null or empty. In all other cases, if a when rule is not found in any other part of the class hierarchy, the system attempts to resolve it against @baseclass.

Valid from Pega Version 8.1

You can now define integration systems that you can use when you create data pages, integration connectors, and databases. Integration systems are associated with an icon that is displayed on the Integration Designer so that you can quickly view the systems that are used by your data types. This information is useful for assessing the effect of migrating to a new system of record and for understanding your data model.

For more information, see Creating an integration system.

Valid from Pega Version 8.1

You can now manage data views, called data pages in Dev Studio, in the Data Designer in App Studio. You can change a data view's data source without switching to Dev Studio. You can create a JSON mapping using a visual, drag-and-drop mapper.

For more information, see Data view management.

Valid from Pega Version 8.1

You can now access a visual depiction of the relationships among data types from the Data Designer in App Studio. By understanding how data types depend on properties and other data types, you can extend your data model more quickly.

For more information, see Viewing data relationships.

Valid from Pega Version 8.1

Use the Integration Designer to manage data at the application level and to access a comprehensive view of all data objects in your application with their associated data. Additionally, from the Integration Designer, you can create data objects and map them to other objects and to systems of record.

For more information, see Managing application data with the Integration Designer.

Valid from Pega Version 8.1

Use the data type wizard in the Integration Designer to create data types and map them to systems of record. The data type wizard reduces complexity when creating and mapping data objects, resulting in reduced development time and a simpler workflow.

For more information, see Mapping fields.

Valid from Pega Version 8.1

For on-premises deployments that use Microsoft SQL Server, set the Pega-Reporting/reporting/useMergeHintForRRquery dynamic system setting to true. If you do not configure this setting, you might not be able to create a new data type in Integration Designer that uses Pega as the system of record. Configure the setting as follows:

  • Owning ruleset: Pega-Reporting
  • Setting purpose: reporting/useMergeHintForRRquery
  • Value: true

For more information about configuring dynamic system settings, see Creating a dynamic system setting.

All Pega product release notes can be found on their product pages.