Published Release Notes

PATCH support for REST integrations

REST connectors and REST services now include support for integrating with REST APIs that require using the PATCH method. REST integrations that support the PATCH method allow you to make partial updates to individual resources while retaining data that does not require an update. With PATCH support, you no longer need to write complex custom code to integrate with services that require using the PATCH method.

For more information about REST integrations, see Connect REST form - Completing the Methods tab.

Configure REST connectors for standard-compliant endpoints

REST connectors now support all standards-compliant endpoint URLs, regardless of how those URLs use query parameters.

This URL support allows you to do the following actions:

• Include repeated query string parameters in a URL.
• Omit a query string parameter if the value of the parameter is empty when you send a request.
• Apply appropriate encoding for different URL components.

For more information about REST connectors, see Connect REST form.

Elasticsearch reports support string comparison operators

To improve performance, reports that use string comparison operators in filters can now run queries against Elasticsearch instead of querying the database. The following operators are now supported for Elasticsearch queries.

• Starts with, Ends with, Does not start with, and Does not end with
• Contains and Does not contain
• Greater than, Less than, Greater than or equal, and Less than or equal

In cases where a query cannot be run against Elasticsearch, the query is run against the database, for example, if the query includes a join. To determine if a query was run against Elasticsearch, use the Tracer and enable the Query resolution event type. For more information, see Tracer event types to trace.

OAuth 2.0 support in Integration Designer

Integration Designer now supports the configuration of OAuth 2.0 authentication with authorization code and client credential grant types. Use OAuth 2.0 authentication when creating a new data type, replacing a data source, or updating a data source.

For more information about REST integrations, see About Connect REST rules, and for more information about OAuth 2.0 Authentication, see OAuth 2.0 providers.

Changes to the Attach Content control in Pega Client for Windows

Users who access offline-enabled Pega Platform™ applications from Pega Client for Windows can now use the Attach Content control within a case view to attach files with a native file picker control or take screenshots with a device camera. Images are immediately attached to the case, and image file names are based on a time stamp. If a device has no camera, the client skips the source selection step and the native file picker control opens.

For more information, see Harness and Sections forms – Adding an Attach Content control.

Support for Firebase Cloud Messaging (FCM) push notifications in Android custom mobile apps

You can now create Android custom mobile apps that use push notifications with the Firebase Cloud Messaging (FCM) services. The push notifications for Android custom mobile apps based on legacy Google Cloud Messaging (GCM) are deprecated, as GCM services will be officially removed from use on April 11, 2019. To continue to use push notifications, you must migrate your custom mobile apps to FCM services. Before building your custom mobile app, you must register your Android app for push notifications in the Firebase console, obtain the FCM server key and Google Services JSON file, and use the key and file in the Android certificate set to build the custom mobile app.

For more information, see Migrating Android custom mobile apps that use push notifications to Firebase Cloud Messaging, Push notifications in Android mobile app, and Android certificate set.

Manage test ID access with an access group role

Test IDs for user interface components are available only to users who have the PegaRULES:TestID role added to their access group. This requirement allows administrators to limit access to test IDs to users who create or run tests. At run time, applications do not include the test ID data for users without the PegaRULES:TestID role, which reduces the amount of code that is downloaded to the client.

For more information see Managing Test ID access with an access group role

PEGA0107 alert enables performance monitoring of offline-enabled apps

You can now monitor the performance of offline-enabled apps by analyzing PEGA0107 alerts from Pega Predictive Diagnostic Cloud™. PEGA0107 alerts are equivalent to PEGA0069 alerts in the context of offline-enabled applications, but PEGA0069 alerts are not generated for offline-enabled applications.

For more information, see PEGA0107 alert: Client page load time for offline-enabled applications and Pega Predictive Diagnostic Cloud Improvement Plan overview.

Improved clipboard performance for editable data pages

Improve clipboard performance for editable data page processing by using the new high-throughput mode option. This mode does not support all clipboard features.

For a list of supported and unsupported features, see Data page rules - Using the Definition tab.

Service Portlet rules are deprecated

Service Portlet rules are deprecated. Existing rules will continue to work, but you cannot create new ones. Use Pega Web Mashup instead. In addition, some changes might impact functionality. If you are using Portlet rules and plan to upgrade, contact your customer service representative.

For more information about Pega Web Mashup, see About Pega Web Mashup.