Published Release Notes

Automatically process cases with Box

You can now use Box to store attachments during automated case processing without requiring user input at run time for authentication or authorization with Box. The authentication profile must be OAuth 2.0 with a grant type of authorization code. You can view which apps are connected, connect apps, and disconnect apps on the Connected apps landing page.

For more information, see Connected apps landing page.

Updates to the Application rule form

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.

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.

Improved contracts for implementations

For more complete contracts, automations now support embedded pages, default values, and picklists. These enhancements provide a more robust model for inputs and outputs that is easier to update and maintain.

For more information, see Viewing automations.

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.

Store and source content in Box

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.

Automatically generate OpenAPI Specification documentation for application REST APIs

You can now access a clear, standard view of all the REST APIs in your application by using autogenerated OpenAPI Specification (OAS) documentation. In App Studio, you can view the OAS documentation generated for application-specific REST APIs by using the new Application tab in the API channel. Additionally, service package rules now include an OpenAPI tab where you can view the automatically generated OAS documentation for all the REST services included in the service package. With these enhancements, you can easily find, visualize, and test the REST APIs in your application.

For more information, see Generating OpenAPI Specification documentation for application-specific REST APIs.

Automatically process cases with SharePoint

You can now use Microsoft SharePoint Online to store and source case and Pulse attachments and to store and source attachments during automated case processing. Users only have to provide authentication and authorization details the first time they access SharePoint Online or when the trust has expired. The authentication profile must be OAuth 2.0 with a grant type of authorization code. The SharePoint Online component can be downloaded from Pega Exchange. For more information, see Downloading and configuring pluggable content management components.

Enhancements to automations for defining Pega API contracts

With enhanced automations, you can now pass embedded pages, specify default values for optional input parameters, and define a set of values for inputs by using the picklist or enumerated field types. The new enhancements make your applications easier to define and maintain, and you can now provide callers of Pega APIs with a clear description of the API.

For more information, see Viewing automations.

Actionable error message in integration wizards

Improvements have been made to the integration wizards for SOAP, SAP, and .NET that enhance the user experience by providing clearer, actionable error messages when there are problems with WSDL uploads; letting you edit the endpoint while creating or testing the integration; clarifying how the data source class layer is reused and removing confusing terms; and adding an option in Tracer to view SOAP messages generated or received by integrations.