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.
Support for configuring data sources by using OpenAPI Specification
Valid from Pega Version 8.6
The Integration Designer in App Studio now supports OpenAPI Specification. You can provide an OpenAPI Specification endpoint or upload a YAML file to automatically generate data sources according to the specification. With this enhancement, you avoid having to manually create a representative sample JSON request and response, saving you time and increasing productivity.
For more information, see Integrating with a REST API by using OpenAPI Specification.
Improved resiliency and observability of email infrastructure
Valid from Pega Version 8.6
Pega Platform now has several enhancements to improve the resiliency and observability of its email infrastructure. With the following enhancements, you can improve service quality and reduce maintenance costs:
- Pega Predictive Diagnostic Cloud alerts notify you of connection timeouts and help you troubleshoot more quickly.
- Default values for email settings ensure that your email configuration is optimal and follows best practices.
- Email listeners automatically retry test connectivity upon start-up if the connection fails or authentication fails.
- Improved logging provides meaningful messages and log categorization to support debugging.
For more information, see List of events and notifications in PDC.
Deprecation of EAR deployments in Pega Platform 8.6
Valid from Pega Version 8.6
Starting with Pega Platform 8.6, EAR deployments of Pega Platform are deprecated. In the upcoming 8.7 release, EAR deployments will not be supported. The following rules that require EAR deployments will also be deprecated and no longer supported in Pega Platform 8.7:
- Connect EJB
- Connect JCA
- JCA Resource Adapter
- JMS MDB Listener
- Service EJB
With this deprecation, you can use the latest tools and keep your application up to date.
Upgrade impact
In Pega Platform 8.6, you can still create rules that require EAR deployments and update existing rules. However, after an upgrade to Pega Platform 8.7, rules that require EAR deployments are no longer supported.
What steps are required to update an application to be compatible with this change?
To prepare your application for this change well in advance of the Pega Platform 8.7 release, see the following table for a list of alternative rules and for guidance on modernizing your application.
| Deprecated rule type | Alternative rule type | Recommended configuration |
| Connect EJB | Connect REST | Substitute legacy EJB resources with a REST API, and use REST connectors to interact with them. |
| Connect JCA | Connect REST | Substitute legacy JCA resources with a REST API, and use REST connectors to interact with them. |
| JCA Resource Adapter | JCA resource adapters are data records that are used within the scope of a Connect JCA rule. If you replaced Connect JCA rules in your application with Connect REST rules, JCA resource adapters are no longer relevant. | No further configuration is necessary. |
| JMS MDB Listener | JMS Listener | Replace JMS MDB Listener configurations with standard JMS Listener configurations. |
| Service EJB | Service REST | Redefine your EJB services as a set of RESTful service APIs, and invoke them over HTTP/HTTPS. |
For information on the supported platforms that are affected by this deprecation, see Pega Platform 8.6 Support Guide.
Legacy Parse XML rule configurations must be upgraded to edit them
Valid from Pega Version 8.6
If your application has Parse XML rules that use the legacy configuration from Pega Platform™ 5.x, you cannot edit these rules after you upgrade to Pega Platform 8.6 until after you upgrade them to use tree-based parse rule configuration.
You must upgrade a Parse XML rule that you want to edit if it shows the following warning when you open it in Dev Studio.
This type of Parse XML rule is deprecated. An upgrade should be performed.
An option to upgrade also displays below the message.
Upgrade impact
Parse XML rules with the legacy configuration do not map data to the clipboard, and the rule definition is empty. After you upgrade to Pega Platform 8.6, you cannot edit Parse XML rules that you created in Pega Platform 5.x or earlier until you upgrade them to use tree-based parse rule configuration.
What steps are required to update an application to be compatible with this change?
Update legacy Parse XML rules to use tree-based parse rule configuration before you edit them in Pega Platform 8.6. Using tree-based parse rules is considered a best practice.
- Open the legacy Parse XML rule.
- On the Mapping tab, click Upgrade.
Result: The Allow tree editing? check box is displayed and is automatically selected. You can add attributes and elements to the tree structure, or delete them. - Save the upgraded rule configuration.
For more information, see Parse XML rules.