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.
Support for sending emails by using Microsoft Graph
Valid from Pega Version 8.6
Email integration with Microsoft Office 365 now supports sending emails by using Microsoft Graph. With this enhancement, you can send email with a more secure protocol that complies with your organization’s security policy.
For more information, see Creating an email account.
Email Wizard support discontinued
Valid from Pega Version 8.4
Pega Platform™ no longer includes the Email Wizard. This wizard helped set up an email service for sending and receiving email in Pega Platform. The wizard generated an email account, an email listener, and an email service rule.
After an upgrade to Pega Platform 8.4 and later, existing clients must create new email accounts and email channels in App Studio. When you configure a new email channel, you add your email accounts so that customers can send and receive email by using the Pega Email Bot. Configuration of an email channel automatically generates an email listener and service email rules.
For more information, see Creating an email account and Building an Email channel.
Support for REST connectors to route network traffic via proxy
Valid from Pega Version 8.6
To easily route network traffic, you can now configure proxy details for individual REST connectors. This enhancement allows you to manage your proxy settings so that you can securely access online resources that lie beyond your proxy servers.
For more information, see Configuring a REST connector.
Connect-HTTP support discontinued
Valid from Pega Version 8.6
Pega Platform™ no longer supports Connect-HTTP rules. HTTP connectors were used to start HTTP request/response interactions between Pega Platform and external systems identified by a Connect HTTP rule (Rule-Connect-HTTP rule type).
After an upgrade to Pega Platform 8.6 and later, you can still use and modify existing HTTP connectors, but you cannot create new ones. As a best practice, use REST connectors instead, which offer more capabilities and have better support from development teams.
For more information, see Connect REST rules.
Data import wizard compatibility with Cosmos applications
Valid from Pega Version 8.6
The data import wizard is now Cosmos-compliant. When you launch the data import wizard as a page, you can leverage the new features provided by Theme-Cosmos, such as adding custom buttons and functionality to your Cosmos applications.
Support for configuring and saving external data in App Studio
Valid from Pega Version 8.6
You can now configure a savable data plan to easily replace or update related data directly from App Studio, and persist those changes during the case lifecycle. This enhancement allows you to work directly in App Studio, without being limited to read-only access of data from case types.
Automation performance enhancements
Valid from Pega Version 8.6
To improve the performance of automation-based REST services and DX APIs, you can now configure JSON inputs and outputs in automation rules. The automation passes the JSON object directly to an automation-based REST service or DX API, eliminating the need to transform data on a page to JSON first. You can also take advantage of this enhancement if you are calling an automation from an activity. Additionally, you can simulate a JSON response in the automation rule and update the JSON sample if needed.
For more information, see <link TBD> and <link TBD>.
Support for creating automations
Valid from Pega Version 8.6
You can now create automations in Pega Platform. By creating an automation, you clearly define a contract to perform a specific task. For example, you can create an automation that retrieves a list of data objects that are available in the application.
For more information, see Creating an automation.
Support for filtering requests and responses in activity-based REST services
Valid from Pega Version 8.6
You can now use a JSON data transform to filter inputs and outputs in activity-based REST services. With this enhancement, you maintain high performance by filtering unnecessary properties from the REST service request and response.
For more information, see Creating a request for POST, PUT, and PATCH methods by using an activity implementation and Creating a response for Service REST methods by using an activity implementation.