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.
Execute Tests service to run all data page unit test cases
Valid from Pega Version 7.2.1
You can now use the Execute Tests service to run a set of tests at the end of build runs. An external validation engine, such as Jenkins, calls the service, which runs all data page unit test cases in your application, and returns the results in XUnit format. Use this service to validate the data in your application and to correct any issues before you deploy your application.
For more information, see Running all data page unit test cases with the Execute Tests service.
Quick and customized data imports
Valid from Pega Version 7.2.1
You can now quickly add, update, or delete data records for your data types by uploading .csv files that contain a large number of records. The bulk import process allows you to import data from a variety of sources and gives you more control over your data. You can customize this process by overriding a data transform to add purposes, a section to add fields, and an activity to define the logic for each purpose.
For more information, see Data import customization.
Enhancements to the REST integration wizard
Valid from Pega Version 7.2.1
You can use the improved REST integration wizard to quickly create data sources in your application. The steps in the wizard are now arranged in a manner that makes the process of creating REST integration more intuitive. You can add custom headers that allow you to connect to complex REST services. You can also enter the name of the system that hosts the REST service, which allows you to group data sources that connect to the same system.
For more information, see the REST integration section in Integration wizards.
Improved security for clipboard pages
Valid from Pega Version 7.2.1
To prevent data leakage and inconsistency, the Pega 7 Platform does not allow properties on a clipboard page to refer to properties on pages with a lower scope. For example, an autopopulate property on a node type clipboard page cannot source data from a data page with scope “requestor” or “thread.”
For more information, see Page scope types for data and declare pages.
Store and source content in Box
Valid from Pega Version 7.2.1
You can now attach content from Box while working on a case in your application. You can attach files directly to your case or include them in a Pulse message. You can also store all the case and Pulse attachments in your application in Box. To enable content sourcing and storage in Box, configure the Content sourcing and Content storage sections on the Integration & security tab of your application rule.
For more information, see Storing and sourcing content in Box.