Secure OAuth 2.0 protocol available for Google Mail integrations

In addition to authentication with basic credentials, SMTP email integrations for Google Mail now support OAuth 2.0 authentication. This enhancement increases your email integration security and integrity with Google Mail server authentication by using an OAuth 2.0 JWT bearer grant type.

For more information, see OAuth 2.0 authentication for email providers.

Self-management of custom certificates for email integrations

Save time by self-managing and configuring certificates that your Pega application uses to connect to an email server. With this enhancement, email accounts now support and store custom certificates for STARTLLS and IMAP protocols, which eliminates the need to update any other configurations.

For more information, see the article that matches your business scenario in the Creating an email integration chapter.

Faster and more accurate OpenAPI Specification with JSON data transforms

For improved performance and greater accuracy of the OpenAPI Specification for Pega Platform, you can now use a JSON data transform in service REST rules to generate the OpenAPI Specification. Instead of displaying all relevant records, the OpenAPI tab displays only the properties that are defined in the JSON data transform, so that you can see the most relevant properties.

For more information, see Best practices for generating OpenAPI Specification documentation.

Searchable data pages

For enhanced search capabilities, you can now configure searchable data pages. With searchable data pages, you can search for data objects that are stored in a remote system. For example, a contact center agent can search for a customer by entering their address in a search field. The search results are populated with the customer who matches the address.

For more information, see Specifying a searchable data page.

Primary fields for enhanced data modeling

In Cosmos React applications, you can define fields as primary directly from your data model, which saves you time by reducing UI configuration. The system automatically generates a Primary fields view that contains the primary fields in your case type or data object. For example, during data modeling, you define basic personal information fields as primary fields, such as name or address, and automatically include them in your cases without the need to modify or create views manually.

For more information, see Configuring primary fields.

Minor enhancements in the file listener configuration

To help with correct file listener configuration, when you use a local path that is Goofys-enabled as the source location, Pega Platform replaces the source location field in the file listener to match the corresponding file specification. As a result, Pega Platform uses the out-of-the-box repository APIs to communicate with the source location at run time.

Additionally, the following guardrails and alerts are now available:

• Guardrail warning for file listener rule configuration on Pega Cloud, which informs users that a cloud environment should not use a local file system as the source location.
• Pega Predictive Diagnostic Cloud alerts that report whether the source path configuration of a file listener does not fit within the guardrails for Pega Cloud.
  Note: Pega Predictive Diagnostic Cloud generates the new alerts during the startup of a file listener instance in a cluster.

Improved performance for DX API calls

To provide improved performance for the DX API version 1 GET /cases/{ID} endpoint, Pega Platform no longer returns the SummaryData metadata in the response by default. If your application requires that data, set the pyExcludeSummaryData application setting to false.

For more information, see Configuring production-level run-time settings.

Improved case locking with DX API

In Cosmos React applications, to limit interruptions to everyday work, locked cases automatically obtain the lock from the previous session for the same user. As a result, you can safely continue working on a case even if your session unexpectedly ends, for example, when your browser closes accidentally. By default, this enhancement applies to DX API version 2 through the pyObtainLockIfSameUser when rule. System architects can override the when rule to apply this functionality to other channels.

Deprecated rule types

Starting with Pega Platform version 8.7, the following rule types are deprecated:

• Connect dotNet
• Connect File
• Connect SAPJCo
• Service dotNet
• Service HTTP
• Service SAPJCo
• Connect EJB
• Service EJB
• Connect Java
• Service Java
• Connect JCA
• JCA Resource Adapter
• Service JSR94
• JavaBean

Update impact

After an update to Pega Platform version 8.7, you cannot create new instances of these deprecated rules. However, you can use and modify existing rules.

What steps are required to update the application to be compatible with this change?

Use the following table to determine alternatives for your deprecated rules:

Deprecated rule	Alternative
Connect dotNet	Connect SOAP rules
Connect File	For on-premises systems, use the D_pxNewFile landing page with the defaultstore repository. For Pega Cloud systems, use the D_pxNewFile landing page with the pegacloudfilestorage repository. For more information, see Repository APIs.
Connect SAPJCo	Connect SAP rules
Service dotNet	Service SOAP rules
Service HTTP	Service REST rules
Service SAPJCo	Service SAP rules

Collaboration icon not available in delegated data types

When an admin user saves a delegated data type in Pega Platform, the collaboration icon displays a pop-up window to refresh the data type in the portal. When the user who works in the portal refreshes the view as a result of the prompt, the data type view changes to the view that is available to the admin user. To prevent unauthorized access to configurations that should only be accessible by admin users, the collaboration icon is now unavailable in delegated data type views.

Update impact

After an update to Pega Platform version 8.7, the collaboration icon is no longer available for delegated data types in portals.

What steps are required to update the application to be compatible with this change?

Users can continue to refresh delegated data types in the following ways:

• In the portal in which the user works, by clicking the Refresh link.
• In Dev Studio, in the delegated data type, by clicking ActionsRefresh.