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.
Skins can inherit formats from a parent
Valid from Pega Version 7.2
Skin inheritance allows a dependent skin to inherit formats and mixins from a parent skin. This feature provides a modular organization of styles, reducing the cost of maintaining skins. You can create a specific mobile skin to include mobile-specific styles and disable unused styles to decrease the size of the CSS. Inherited formats are displayed on the Inheritance tab of the skin. Formats that are specific to the skin are displayed on the My formats tab.
For more information, see Skin inheritance.
Paginated lists in repeating dynamic layouts
Valid from Pega Version 7.2
Repeating dynamic layouts can now display paginated lists. Pagination reduces the cost of loading the entire list onto the browser. You configure pagination on the General tab of the layout properties.
For more information, see Dynamic Layout Properties - General tab.
Heading level support
Valid from Pega Version 7.2
You can configure heading levels for containers that support headings. Headings facilitate accessibility by making the UI understandable to assistive technologies. You can edit headings in the Base settings tab of the skin.
For more information, see Base settings.
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.