Published Release Notes

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.

Enhancements to the Send Email smart shape

The following enhancements have been made to the Send Email smart shape:

• You can now configure the Send Email smart shape in Pega Express.
• You can use templates, such as a rejection template, in your email.
• You can use property values, which allow you to insert the value of a field in your case type, such as First Name, within the email.
• You can insert a link to the case ID in your email.
• You can more quickly configure your recipient list by using two options, instead of one, to send messages to either a list of email addresses or to fields.
• You can choose to send either all case attachments in an email, or you can send attachments of a specified attachment category or an attachment type field. You can specify multiple attachment categories and attachment type fields.

For more information, see the following help topics:

• Sending email from a case (Pega 7.3)
• Sending email from a case (Pega 7.3 express)

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.

Requestor pools management in Designer Studio

On the new Requestor Pools landing page, you can view and manage requestor pools across the cluster, including on the current node and remote nodes. By using this landing page, you can tune the requestor pools to improve the performance of services. You can clear the requestor pool for a service package and view the requestor pool basic metrics and configured thresholds.

For more information, see Requestor pools management, Clearing a requestor pool, Viewing details for a requestor pool, Tuning a requestor pool configuration.

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.

Post files and links with pxPostMessage API

The pxPostMessageAPI now supports text messages, file attachments, and hyperlinks. You can programmatically update Pulse streams using this API from activities or SLA rules.

Extended support for Cosmos React tables in Pega Infinity applications

Cosmos React tables are now available to Pega Infinity™ pages. Previously, when you enabled Cosmos React UI for landing pages in your application, you could add the React-based tables only to landing pages. With this enhancement, you can also embed tables in a section that is part of your case view or dashboard page.

For more information, see Adding a React table to a section.

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.