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.

Geolocation tracking for the latest mobile client

Valid from Pega Version 8

The latest version of Pega Mobile Client™ now supports geolocation tracking for offline-enabled mobile apps. You can enable constant tracking when users work on specific cases from their worklists. This enhancement helps audit the trail of the case and increase the efficiency of your mobile users. For example, dispatchers at headquarters can track the routes of field workers and more effectively assign them tasks based on their current location.

For more information, see Tracking mobile users based on geolocation data.

Supported JDBC drivers

Valid from Pega Version 7.1.1

Pega 7.1.1 supports Java 6 and Java 7 SDKs only. Ensure that the JDBC driver you are using supports those versions of Java. See your database installation or upgrade documentation for additional information.

DatabaseJava 6Java 7
Oracleojdbc6.jarojdbc7.jar
MSQLsqljdbc4.jarsqljdbc4.jar
DB2 LUWdb2jcc4.jardb2jcc4.jar
DB2 z/OS*db2jcc4.jar or jdb2jcc.jar**db2jcc4.jar
PostgreSQLpostgresql-9.1-903.jdbc4.jar***postgresql-9.1-903.jdbc4.jar

* JDBC drivers are only available from the DB2 for z/OS product. Additionally, you need db2jcc_license_cisuz.jar in the same directory as db2jcc4.jar.

** The db2jcc.jar has been deprecated and may not be supported in future releases.

*** This .jar file is required for PostgreSQL version 9.1.x.

Deprecated end user portals

Valid from Pega Version 7.1.1

The following portals are no longer be supported:

  • SysAdmDD
  • WorkUserDD
  • WorkManagerDD

As a best practice, customize standard, supported portals rather than update your existing portals to include new features.

Support for Data streaming service for Pega Cloud Marketing 7.4 applications

Valid from Pega Version 2.1

Pega Cloud Marketing 7.4 applications support the Kafka-based Stream service featured in Pega Platform 7.4.

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.

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