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.

Unified Messaging Desktop integration with Pega Platform

Valid from Pega Version 8.4

You can now use the Pega Unified Messaging Desktop™ customer service solution with a Pega Platform™ application so that customer service representatives (CSRs) and other users, such as managers, can respond to user requests more quickly and in a more consistent manner. With integrated Pega Unified Messaging Desktop, CSRs can escalate user requests from Pega Intelligent Virtual Assistants™ (IVAs) by using case processing and artificial intelligence alongside Pega Customer Service™

For more information, see Develop a single IVA channel to chat across different messaging platforms.

Strategies are now available as a condition type in proposition filters

Valid from Pega Version 8.4

When designing proposition filters, you can now include strategy outcomes as a condition to be evaluated. Select a strategy and specify the component that you want to use as output to include more advanced decisioning in your proposition filters.

For more information, see Enrich your Proposition Filter rules with conditions based on strategy results.

Client-server deployment of Hazelcast

Valid from Pega Version 8.4

Pega Platform now supports the client-server model for the Hazelcast service, which provides cluster communication and distributes Pega Platform features across nodes. This optional deployment model introduces independent scalability for both servers and clients in Pega Platform, improving stability for deployments that use a large number of nodes.

The Hazelcast client-server model is intended for select environments running Pega Platform 8.4 across a large number of nodes and should be deployed only when directed by Global Client Support.

Improved mobile app user experience

Valid from Pega Version 8.4

Pega Platform™ can now produce a better mobile experience through performance gains and flexible access settings. Apps now support quick-loading native worklists, smooth scrolling and swiping, and query-based search, which improve productivity for mobile users. In addition, you can make your app available to users without authentication, and enhance usability for products that do not require strict security controls.

For more information, see Securing mobile apps.

Default text analytics model for detecting small talk

Valid from Pega Version 8.4

Enhance your web chat experience by configuring chatbots to detect small talk. Pega Platform™ provides the default model that is a topic detection model, available for English, German, Spanish, Dutch, Portuguese, Italian, and French.

For more information, see Configure your chatbot for small talk.

More efficient mobile development

Valid from Pega Version 8.4

The work environment for mobile app developers in Pega Platform™ is now more intuitive. Because every new out-of-the-box application now comes with a preconfigured mobile channel, you can start building mobile apps straight away. Create a mobile channel from scratch, and then customize it to include specific requirements for your new app.

The following updates enhance the process of building mobile apps:

  • Your application stores all mobile channels as rules. You can reuse these channels across all versions of your mobile apps for more convenient updates.
  • You can now configure contextual search from the mobile channel.
  • You can now create native mobile list pages for the app navigation directly from the mobile channel.
  • You can now add pages from web portals to a mobile app navigation pane, with full support for native mobile features, such as floating action buttons.
  • Mobile channels now support configuration through predefined templates, widgets, and actions.
  • You can now instantly preview your mobile channel configuration to see how the app displays on mobile devices.
  • Configuration of offline support for mobile apps is now available from a single, low-code page.
  • The preview section now offers a low-code pane, from which you can instantly start building a mobile app.
  • The mobile channel now supports adding custom iOS and Android modules.
  • Admin Studio now supports a mobile page, from which you can provide your own Mobile Build Server credentials and decide whether users need to provide authentication to download your mobile app.

Expanded checks for Java injection vulnerabilities (8.4)

Valid from Pega Version 8.4

The Java injection vulnerability check feature has been enhanced in Pega Platform™ to further prevent Java injection, including Edit validate, Edit input, and JSP rules. Pega Platform reports errors at design time and run time, and does not run any rule that includes any of the following Java code:

  • JavaCompiler
  • new ProcessBuilder()
  • org.dita.dost.invoker
  • Runtime.getRuntime()

For more information, see Configuring the Java injection check.

Improved offline support for mobile apps

Valid from Pega Version 8.4

The updated offline mode in Pega Platform™ now reduces implementation time, enhances the development process, and helps you create a more comprehensive mobile experience for users without a reliable web connection.

The improved offline support includes the following enhancements:

  • Offline-enabled apps now use native mobile UI components, such as headers and bottom bars.
  • Offline mode now supports decision trees for improved case processing. 
  • Users can now process multiple cases simultaneously in separate offline tabs, which leads to higher productivity.
  • Offline-enabled apps now work more efficiently because of improved caching and background synchronization.

For more information, see Working with offline apps.

Integrate your application with external Kafka clusters

Valid from Pega Version 8.4

Configure your application to use an external Kafka cluster for managing real-time data. By having an external Stream service provider, you can perform such maintenance tasks as an upgrade or hotfix deployment faster because external nodes do not require restarting.

For more information, see Externally managed Stream service.

Updated architecture of the data flow service

Valid from Pega Version 8.4

Benefit from improvements to data flow architecture that increase the stability of data flow runs and minimize the need for manual restarting of data flow jobs. Real-time data flows now use improved node rebalancing for better handling of failed or restarted nodes. If the topology changes, batch data flows no longer attempt to pause and resume the run. As such, there are fewer interactions with the database and between the nodes, resulting in the increased resilience of the Data Flow service.

If you are upgrading from a previous version of Pega Platform™, see Changes to the architecture of the Data Flow service for an overview of the changes to the Data Flow service compared to previous versions.

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