Published Release Notes

Support for OAuth 2.0 authorization code grant type

Pega Platform™ now supports the OAuth 2.0 authorization code grant type, which allows Pega Platform to act as an OAuth 2.0 access token provider for native applications on mobile and other devices. By using the authorization code grant type for mobile clients, you no longer need to implement a variety of standards for various authentication providers. The authorization code grant type also supports the Proof Key for Code Exchange standard (PKCE) for securing public clients.

For more information, see Creating and configuring an OAuth 2.0 client registration.

Use client-based access control to support EU GDPR requirements

You can use client-based access control (CBAC) to satisfy the data privacy requirements of the European Union General Data Protection Regulation (GDPR) and similar regulations. By using client-based access control, you can identify the personal data of clients and automatically process requests to view, update, or remove the data in a secure manner. You can also enforce restrictions on the use of this data in application functions.

For more information, see Client-based access control.

Data pages can source information from a robotic desktop automation

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.

Supported artifacts section removed from repository rule form

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.

Support for character data type on local variables in activities deprecated

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.

When rule might not resolve against @baseclass

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.

New integration system resource

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.

Data view management added to Data Designer

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.

View data type relationships in Data Designer

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.

Data encryption support for system data

You can now control system-level data security by using data encryption in Pega Platform™. Encryption of system-level data improves the overall security of your system.

For more information, see Configuring the platform cipher and Configuring a keystore for a master key from a custom source.