Updates to the Authentication Profile rule form
Valid from Pega Version 7.2
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
Valid from Pega Version 7.2
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
Valid from Pega Version 7.2
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
Valid from Pega Version 7.2
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
Valid from Pega Version 7.2
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
Valid from Pega Version 7.2
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.
Atom Server and SOAP Server rule forms are deprecated
Valid from Pega Version 7.2
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.
Create SAP integration of IDoc type
Valid from Pega Version 7.2
You can now create data sources in your application based on IDoc XSD documents by using the New SAP Integration wizard. The system generates data and integration layer records that are required to use the data sources.
For more information, see SAP integration by using IDoc XSD documents.
Updates to the Connect SAP rule form
Valid from Pega Version 7.2
You can use the enhanced Connect SAP rule form to create or update SAP connectors of type IDoc. On the Service tab of this rule form, specify or create an XML stream that represents an IDoc XSD input document, which describes the external SAP service.
For more information, see SAP integration by using IDoc XSD documents.
Updates to the Data Page rule form
Valid from Pega Version 7.2
You can use the enhanced Data Page rule form to specify the name of a source system in the System name field in the Data sources section. This field represents the name of the system that is associated with a data source. For example, if your data source is a REST connector that connects to an external weather service such as Google Weather API, you can enter Google Weather in the System name field for the data source. The system name is used to display the source systems for a data type on the External Data Entities landing page.
For more information, see Viewing external data entities.