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.
Show multiple views of data in your application
Valid from Pega Version 7.2.2
You can now show multiple views of data in your application by adding the record editor (pxRecordsEditor) section to a layout, another section, or a cell in a layout. You can configure the section to customize the display and enable the search, import, and export capabilities of the record editor.
For more information, see Multiple views of data in the record editor section.
Support for additional rule types for PegaUnit test cases
Valid from Pega Version 7.2.2
To compare the expected results with the results that are returned by running a rule, you can now create PegaUnit test cases for the following rule types:
- Activities
- Data transforms
- Strategies
- Decision trees
- Decision tables
After you unit test these rules, you can convert them to test cases and configure assertions on the test cases. You can also set up the clipboard with data before tests are run, and clean up the clipboard after tests are run.
For more information, see PegaUnit testing.
Page assertions are supported for PegaUnit test cases
Valid from Pega Version 7.2.2
You can now create page assertions for PegaUnit test cases. Because data transforms and activities can create or remove pages, you can configure page assertions to determine whether a page exists after you run PegaUnit test cases.
For more information, see Configuring page assertions.
Authenticate REST data sources by using OAuth 2.0
Valid from Pega Version 7.2.2
You can now authenticate the data sources that are created from your REST integration by configuring OAuth 2.0 authentication in the New REST Integration wizard. You can specify or create an OAuth 2.0 authentication profile in the wizard by using the client credentials or authorization code grant type.
For more information, see OAuth 2.0 in REST integration.
Customized data imports
Valid from Pega Version 7.2.2
You can now further customize the data import process in Data Designer by:
- Setting a default import purpose and preventing the selection of an import purpose to speed up frequent imports of the same kind
- Removing the import purposes that you do not need for your data type
- Defining a default field mapping between the fields in the .csv file and the fields in your data type that act as a unique identifier (key), to save time during the import process
- Skipping the import progress screen and showing progress contextually within your application
- Including the link for data import anywhere in your application or calling it in the background from a service or agent
For more information, see Data import customization.