Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

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.

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.

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.

Improved processing of correspondence details

Valid from Pega Version 8.6

When you send correspondence, the system now does not update the pxSendDateTime property on the pxCorrSummary work page that belongs to pyWorkPage. In previous versions of Pega Platform™, after sending correspondence, the update of the pxSendDateTime property could cause errors when working with an application at run time. To prevent such issues, Pega Platform now includes a pyEnableCorrSummary when rule that, by default, is set to false. If your business scenario requires updating the pxCorrSummary work page, set the when rule value to true.

For more information, see:

Support for picklists with parameterized data pages in App Studio in Cosmos React UI

Valid from Pega Version 8.6

You can now use data pages with parameters to populate a property of the picklist type with filtered results in App Studio. For example, in a survey case type, you can use a parameterized data page to configure cascading drop-down controls in which the values in a secondary drop-down list are based on the value that the user selects in the primary drop-down list. With dynamically-sourced picklists, you get greater flexibility in configuring picklists, and users see more accurate values.

For more information, see link Dropdown control Properties — General tab.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us