Published Release Notes

Current parameter page can now be passed into activities, collections, and data transforms

In collection rules, you can now pass the current parameter page into an activity, data transform, or another collection when you call the activity, data transform, or collection from either a primary or a response action instead of setting up parameters before you call one of these types of rules. The Pass current parameter page check box is now supported on the Collection rule form.

For more information, see Rules and methods supported by a collection.

Improved modularity of case life cycles

You can add processes to a stage in the life cycle of a case. By organizing related steps into processes, you can design a life cycle that is modular and easy to reuse. This change also makes it easier for stakeholders to understand the flow of events when reviewing your case types.

For more information, see Modular life cycles for cases.

View external data entities in one location

The External Data Entities landing page provides a consolidated view of all the existing data entities in your product. You can access this page by clicking Designer Studio > Data Model > View external data entities. Use this landing page to identify the data sources that are readily available to use and the sources that need to be replaced with production data sources.

Enhanced data modeling

You can now create data types quickly in the Pega 7 Platform and in Pega Express. Use the enhanced Data Designer user interface to define the data model for your data types. More field types have been added, and they are categorized as simple, fancy, and complex to meet your data modeling needs.

For more information, see Data Designer enhancements.

Updates to the Authentication Profile rule form

You can now create OAuth 2.0 authentication profiles by using the enhanced rule form. For this profile type, you can select an OAuth 2.0 Provider data instance, a grant type, and the client information that you obtained from your OAuth 2.0 provider, such as Box or Facebook. You can also revoke issued access tokens on this rule form.

For more information, see Access protected API resources by using OAuth 2.0.

Authorization code grant for OAuth 2.0 providers

You can now connect to OAuth 2.0-protected APIs by selecting the authorization code grant type on the OAuth 2.0 Provider rule form. Enter the authorization code, access token, and revoke token endpoints as indicated by your OAuth 2.0 provider, for example, Box or Facebook.

For more information, see Access protected API resources by using OAuth 2.0.

Information Mashup section for OAuth 2.0 provider authorization

You can now add an Information Mashup (pxInformationMashup) section to a layout, a region, another section, or a cell in a layout to delegate access to OAuth 2.0-protected resources. Configure the section with an OAuth 2.0 authentication profile, mashup section, and authorization section to connect to an external application at run time. For example, users can log on to Facebook from the Pega 7 Platform by using this section and access photographs in their Facebook account.

For more information, see Access protected API resources by using OAuth 2.0.

Updates to the Application rule form

On the Integration & security tab of the Application rule form, you can configure your application to access, store, and manage versions of case attachments in ECM repositories that support the CMIS specification. You can enable CMIS content storage, CMIS content sourcing, or both for your application.

For more information, see Case attachment versions in CMIS repositories.

Manage versions of case attachments in CMIS repositories

You can now access, store, and manage versions of case attachments by using external ECM repositories that support CMIS. You can check out, lock, and locally edit a case attachment that is stored in an external ECM repository that supports CMIS. You can also check in the case attachment to create a new version of the attachment.

For more information, see Case attachment versions in CMIS repositories.

Updates to the Connect CMIS rule form

You can now use the enhanced Connect CMIS rule form to define connections to ECM repositories that support the CMIS specification. On the Service tab, select an existing CMIS provider or configure a custom provider and enter the server type, server URI, and authentication profile to connect to your CMIS provider.

For more information, see Case attachment versions in CMIS repositories.