Published Release Notes

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.

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.

Create SAP integration of IDoc type

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

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

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.

Data pages can source information from a robotic desktop automation

You can now configure data pages to source information from robotic desktop automations (RDA). Using an RDA to source a data page allows you to connect your Pega Platform™ application to any application that is accessible from an end-user's desktop. By using automations to retrieve data and load it into a data page, you can use data virtualization to separate your Pega Platform data model from the physical interface of a legacy system against which the automation is running.

For more information, see Obtaining information from robotic automations.

Supported artifacts section removed from repository rule form

The Supported artifacts check box has been removed from the repository rule form. Developers can use repositories to provide centralized storage, versioning, and metadata support for application artifacts.

For information about repository connections, see Creating a repository for file storage and knowledge management.

Support for character data type on local variables in activities deprecated

Support for the character data type for local variables in activities is deprecated. Use the string data type instead.

For more information about activities, see Activities.

When rule might not resolve against @baseclass

In the rare case in which a step page context is null, or the pxObjClass associated with the step page is empty, the system no longer attempts to resolve the when rule against @baseclass. As a result, you might see more rule not found errors. Check the step page context and class and ensure that they are not null or empty. In all other cases, if a when rule is not found in any other part of the class hierarchy, the system attempts to resolve it against @baseclass.

New integration system resource

You can now define integration systems that you can use when you create data pages, integration connectors, and databases. Integration systems are associated with an icon that is displayed on the Integration Designer so that you can quickly view the systems that are used by your data types. This information is useful for assessing the effect of migrating to a new system of record and for understanding your data model.

For more information, see Creating an integration system.