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.

Improvements to email case triaging

Improvements to Pega Intelligent Virtual Assistant™ (IVA) for Email make the system more robust and user friendly. When you reply to emails in a triage case, you can forward the email, reply to all, and use the carbon copy (cc) and blind carbon copy (bcc) fields. You can also send Pulse messages to discuss an email case without exposing the information to external users. You are notified in the Email Manager and Case Manager portal if you receive Pulse messages. Even when an email case has been resolved and appears as read-only, you can still send Pulse messages.

For more information, see Email Manager portal and Email triage.

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.

Improvements to the Email channel configuration and content analysis

To make the Intelligent Virtual Assistant™ (IVA) for Email more useful and easier to manage, you can track all the Email channel configuration changes that you or other operators make. The system now also detects defined entities and topics, not only in the contents of the email messages and its attached files, but also in the email subject field which improves the responsiveness of IVA to emails. You can map same text that appears in an email triage case to different entities. In previous versions of Pega Platform, only the email body was analyzed but with subject analysis, now the entire email is analyzed for topics and entities, including its salutation and signature.

For more information, see Tracking configuration changes in the Email channel and Enabling the analysis of subject field content during email triage.

Facebook and Web Chatbot configuration in the preview console

When you develop a Pega Intelligent Virtual Assistant™ (IVA) for Facebook or Web Chatbot, you can now teach interactive bot conversations by chatting with the bot in the preview console and guiding the artificial intelligence algorithm to the right responses. This ability greatly accelerates conversation development and simplifies configuration, while providing the developer with more transparency in the mechanisms that produce specific responses.

For more information, see Simulating a conversation and building a chatbot runtime and Testing and building a chatbot from the preview console.

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.

Deprecated metadata types in the Connector and Metadata wizard

The WSDL, SAP WSDL, and DTD metadata types have been deprecated in the Connector and Metadata wizard. For WSDL, use SOAP integration, and for DTD, use XSD.

For more information about SOAP connectors, see About Connect SOAP rules. For more information about XSD, see About the Connector and Metadata wizard.