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.

Case-insensitive filtering in reports

Valid from Pega Version 8.2

Filtering in reports is now case-insensitive, improving the reporting and searching experience. You can turn off case-insensitive filtering, for example, by using an activity. You might want to do this if your index is too big or if the length of time it takes for indexing impacts performance.

For more information on report filtering, see Editing filter conditions.

Add subspaces within spaces

Valid from Pega Version 8.2

You can now create subspaces within spaces. By adding a subspace, you can collaborate on a subtopic that is related to the topic of the parent space. For example, you can create an Annual Day subspace within the Events space.

For more information, see Creating a subspace.

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.

Support for sourcing case and Pulse attachments from repositories

Valid from Pega Version 8.2

You can now source case and Pulse attachments from repositories, which provides a complete solution for attachment management. In addition, unlike other external sourcing solutions, repositories do not require OAuth 2.0 authentication, so that you can connect to repositories that use non-interactive authentication.

For more information, see Configuring external sourcing options for attachments

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.

Add varied content to a case with Recent content gadget

Valid from Pega Version 8.2

In an end user portal such as Case Manager, you can now add any type of file to your case by using a Recent content gadget. You can create documents by using a rich text editor, uploading existing files, or attaching URL addresses. Collaborate on all types of content with other members of your team by providing the necessary documents for your case.

For more information, see Adding content to a space (for App Studio), Adding content to a space (for Dev Studio).

Improvements to email case triaging

Valid from Pega Version 8.2

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.

Predictive models monitoring

Valid from Pega Version 8.2

In Prediction Studio, you can now monitor the predictive performance of your models to validate that they make accurate predictions. Based on that information, you can re-create or adjust the models to provide better business results, such as higher accept rates or decreased customer churn.

For more information, see Monitoring predictive models.

Kafka custom serializer

Valid from Pega Version 8.2

In Kafka data sets, you can now create and receive messages in your custom formats, as well as in the default JSON format. To use custom logic and formats for serializing and deserializing ClipboardPage objects, create and implement a Java class. When you create a Kafka data set, you can choose to apply JSON or your custom format that uses a PegaSerde implementation.

For more information, see Creating a Kafka data set and Kafka custom serializer/deserialized implementation.

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