Published Release Notes

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.

Column Populator utility documentation out of date for prior versions

The documentation for using the Column Populator utility to populate newly exposed database columns is out of date for Pega 7 Platform versions prior to 7.2. For all Pega 7 versions, refer to the Pega 7.2 help documentation for instructions about how to use this utility.

Quickly make a calculation based on a repeating field group

After you add a calculated (read-only) field to a form, you can create simple calculations that reference numeric fields within repeating groups. The expression can use common functions (Sum of, Average of, Minimum of, or Maximum of) or can be a custom expression.

For more information, see Calculations based on a repeating field group.

Add validation to fields on a form

You can now validate the values of single-value fields when you build a form. You can also provide messages that are displayed to users when any condition fails.

For more information, see Field validation on a form.

Atom Server and SOAP Server rule forms are deprecated

The Atom Server and SOAP Server rule forms are deprecated. Use the Connect CMIS rule form instead.

Existing rules that were created with the deprecated forms still work, but you cannot create new ones.