PATCH support for REST integrations
Valid from Pega Version 8.2
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
Valid from Pega Version 8.2
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
Valid from Pega Version 8.2
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
Valid from Pega Version 8.2
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.
Improved clipboard performance for editable data pages
Valid from Pega Version 8.2
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.
Support for the POST method in Integration Designer
Valid from Pega Version 8.2
From Integration Designer, you can now source data from any REST endpoint that requires a POST method to retrieve information. With the POST method, you can encrypt sensitive information in the body of the request.
For more information about using the POST method, see the POST method section on Service REST form - Completing the Methods tab.