Improved data page performance
Valid from Pega Version 8.4
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
Valid from Pega Version 8.4
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
Valid from Pega Version 8.4
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
Valid from Pega Version 8.4
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
Valid from Pega Version 8.4
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
Valid from Pega Version 8.4
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
Valid from Pega Version 8.4
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
Valid from Pega Version 8.4
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.
Updated default dynamic system setting for requestor pools
Valid from Pega Version 8.4
Clients can now enable or disable requestor pools for processing service requests using a new dynamic system setting called EnableRequestorPools with Pega-IntegrationEngine as the owning rulest. Previously, all deployments utilized requestor pools to improve service processing response efficiency; requestor pools eliminated overhead by automatically returning a requestor to the pool after it fulfills a service request. Starting in Pega Platform 8.4, requestor pools are disabled in Client-managed cloud deployments, since these deployments use autoscaling to handle service request traffic. Enabling requestor pools in Kubernetes environments is not recommended, because they can inhibit the default autoscaling settings in the environment.
Requestor pools remain enabled by default in Pega Cloud and on-premises environments.
To help clients navigate this change, Pega has updated its best practice guidance for configuring requestor pools. For an overview, see Requestor pooling for services. For guidance on the use of requestor pools in your application, see the EnableRequestorPools entry in Dynamic system settings data instances.
Upgrade impact
Requestor pools are disabled by default in Pega Platform 8.4 in client-managed cloud deployments. Clients who deployed previous versions of Pega Platform on a Kubernetes environment and who upgrade to Pega Platform 8.4 could see that their services behave differently.
What steps are required to update the application to be compatible with this change?
If clients that are deployed in a Client-managed cloud environment need to configure their services to use requestor pools and they understand how to configure requestor pools for their optimized use, these clients can re-enable requestor pools. Clients should review the best practice for configuring requestor pools before they re-enable requestor pools. To re-enable requestor pools, you modify the EnableRequestorPools setting in the Pega-IntegrationEngine Owning ruleset from “disabled” to Enabled [no value]. For details, see Editing a dynamic system setting.
Gadget configuration by using IAC gateway console is no longer supported
Valid from Pega Version 7.2.1
The Internet Application Composer (IAC) gateway was deprecated in Pega Platform™ 7.2.1 and is no longer supported. The IAC was used to embed a Pega Platform application, such as a gadget, on the pages of a web application that was located on your intranet, extranet, or internet site.
Upgrade impact
After an upgrade to Pega Platform 8.5, the configuration of gadgets through the IAC gateway console is no longer supported.
What steps are required to update the application to be compatible with this change?
To make subsequent changes to your current web mashup, use Pega Web Mashup.
For more information, see Tutorial: Creating a mashup with Pega Web Mashup.