Published Release Notes

Internet Application Composer (IAC) renamed to Pega Web Mashup

The name of Internet Application Composer (IAC) has changed to Pega Web Mashup.

For more information, see Pega web mashups for embedding Pega Platform UI in external web pages.

FTP server records enhanced for SSH FTP

When using SSH FTP (SFTP) in an FTP Server record, you can securely transfer files by using SSH keys. You can enable and configure SFTP by opening the FTP server record and completing the fields in the Protocol section.

For more information, see SSH FTP for FTP server records.

Improved data page performance

Data pages that are sourced from report definitions now support server-side paging. This functionality optimizes the performance and memory of data pages, making them more efficient at retrieving large lists of data. In addition to getting page indicators at the top of a grid, you can sort and filter columns in a grid in conjunction with paging. If you want the system to use server-side pagination, you can also enable pagination from the Data page rule form.

For more information, see Defining data page access.

Email supports Microsoft Graph

Email integration with Microsoft Office 365 now supports Microsoft Graph. By using Microsoft Graph, you can process inbound email more securely and avoid using less secure protocols, such as IMAP and POP3.

For more information, see Creating an email account.

Email listener enhancements for faster email processing

Enhanced email listeners now process more emails in less time. To increase throughput, you can configure email listeners to process several emails simultaneously, instead of one at a time.

For more information, see Creating an email listener.

Support for data page aggregation

You can now aggregate data from multiple sources for faster and easier implementations. With this feature, you can load data pages more easily without using an activity or data transform. 

For more information, see Creating a data page. 

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.

Enhanced OpenAPI Specification generation

To better understand the purpose of your REST API, you can now generate a more complete OpenAPI Specification (OAS) from REST service rules in Pega Platform™. The system uses relevant records to build an accurate schema definition for page and page list outputs, and generate stronger schema type definitions for all inputs, outputs, and fields, such as array or boolean. You can also generate OAS by mapping values to JSON or Clipboard in the request, or mapping values from JSON or Clipboard in the response. 

For more information, see Service REST rules.

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.

Autopopulated properties support savable data pages

To more easily source data, you can now save an autopopulated property that references a savable data page. For properties that you autopopulate by copy, save plans now execute on the copy, instead of on the data page. These enhancements reduce implementation time and make the applications that you build more manageable.