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.

Removal of Pega Mobile Client 7

Valid from Pega Version 8.5

You can now use a single Pega Mobile Client™ that improves app performance, app development, and meets all your mobile needs. With the introduction of new functionalities for mobile apps, Pega Mobile Client 7 is removed in Pega Platform™ 8.5.

Upgrade impact

After an upgrade to Pega 8.5, you can no longer build mobile apps based on Pega Mobile Client 7, and existing apps based on Pega Mobile Client 7 no longer connect to Pega Platform. App developers can now configure mobile apps with Pega Mobile Client.

What steps are required to update the application to be compatible with this change?

Existing clients that upgrade to Pega 8.5 are automatically switched to Pega Mobile Client.

Limits on active data flow runs

Valid from Pega Version 8.5

You can now configure a maximum number of concurrent active data flow runs for a node type. Set limits to ensure that you do not run out of system resources and that you have a reasonable processing throughput. If a limit is reached, the system queues subsequent runs and waits for active runs to stop or finish before queued runs can be initiated, starting with the oldest.

For more information see, Limit the number of active runs in data flow services (8.5).

Upgrade impact

If you have many data flow runs active at the same time, you might notice that some of the runs are queued and waiting to be executed.

What steps are required to update the application to be compatible with this change?

You do not have to take any action. After the active runs stop or finish, the queued runs start automatically. The default limits are intended to protect your system resources, and you should not see a negative impact on the processing of data flows. However, if you want to allow a greater number of active data flow runs to be active at the same time, you can change the limits. For more information, see Limiting active data flow runs.

Web portal reuse removed from the mobile channel

Valid from Pega Version 8.5

The reuse of web portals for creating mobile apps with a single web view is no longer supported. You can conveniently update your existing channels that reuse web portals to take advantage of the multiple-views experience and native mobile capabilities, such as native mobile list views or floating action buttons.

Upgrade impact

The Reuse web portal option is removed from Pega Platform 8.5 and later.

What steps are required to update the application to be compatible with this change?

App developers need to use the migration tool available on the mobile channel to move their apps to the recommended new navigation designer. When users open existing mobile channel with the Reuse web portal option configured, they are prompted to run through the wizard to upgrade the mobile channel to the latest Pega Mobile Client based configuration. When this is done, app developers should rebuild the app.

 

External data flow rules are deprecated

Valid from Pega Version 8.5

External data flows are now deprecated and no longer supported. To improve your user experience with Pega Platform™, the user interface elements associated with these rules are hidden from view by default. Identifying unused features allows Pega to focus on developing and supporting the features that you need.

For more information, see Deprecated: External data flows.

Visual Business Director data is automatically cleaned after a retention period expires

Valid from Pega Version 8.5

To avoid negative impact on system resources, such as memory and disk space, Pega Platform™ automatically cleans out collections data accumulated in Visual Business Director after the time period specified in the vbd/dataRetentionTimeout dynamic system setting.

Upgrade impact

In versions of Pega Platform earlier than 8.5, collections data was not automatically removed. From version 8.5, the data is removed after 465 days (15 months) by default.

What steps are required to update the application to be compatible with this change?

If the default data retention period does not meet your requirements, you can change it by editing the vbd/dataRetentionTimeout setting.

For more information, see "Configuring the data retention period for Visual Business Director" in the Pega Customer Decision Hub 8.5 Upgrade Guide on the Pega Customer Decision Hub product page.

Native synchronization indicators for offline-enabled mobile apps

Valid from Pega Version 8.5

Offline-enabled mobile apps now include a set of native synchronization indicators. Indicators keep users informed about the data synchronization status, for example, the Syncing indicator appears when an app regains network connectivity and starts receiving responses from the server. You can customize the indicators to better suit the look and feel of your mobile app. For more information, see Customizing synchronization indicators.

Upgrade impact

After upgrading Pega Platform™ to version 8.5, your app does not include native synchronization indicators until you update your application to use UI-Kit 15.

What steps are required to update the application to be compatible with this change?

Update the UI Kit in your application to version 15. For more information, see Updating the UI Kit in your application.

Uploading customer responses into adaptive models is no longer available

Valid from Pega Version 8.5

The option to train adaptive models by uploading a static list of historical interaction records has been deprecated in Pega Platform™ 8.5.

Upgrade impact

In versions of Pega Platform earlier than 8.5, it was possible to train an adaptive model by uploading historical data of customer interaction. After the upgrade to version 8.5, this option is no longer available.

What steps are required to update the application to be compatible with this change?

Use data from a report definition to train adaptive models. For more information, see Training adaptive models.

Support for validations in Declare Expression rules

Valid from Pega Version 8.5

Pega Platform™ now correctly evaluates validations on target properties in Declare Expression rules. As a result, any validations defined on properties that have Declare Expression rules in previous releases, now work correctly. 

Upgrade impact

Any unintended validations on properties that have configured Declare Expression rules, both default and user-defined, might cause issues in an application upon saving work objects and data objects that refer to Declare Expression rules.

What steps are required to update the application to be compatible with this change? 

If you experience issues when saving objects, debug your application by setting the declareexp/target/validation/disable dynamic system setting to true. If your application works correctly after the change, it means that validations on Declare Expressions cause the issues. For your application to work correctly, analyze the log files and remove any unintended validations.

For more information, see Declare Expression rules.

Upgraded selected third-party JAR files to support Pega Platform functionalities

Valid from Pega Version 8.6

Pega Platform™ 8.6 now provides upgraded versions of the JAR files that support various functionalities within the Platform, such as generating documents or PPTX files.

Upgrade impact

If you have custom implementations and use any classes from the upgraded JAR files directly in your code or through JAR APIs, after your upgrade to Pega Platform 8.6, your application might experience unexpected run-time behavior if the upgraded JAR version lacks any elements from the previous version. For example, custom implementations can typically include activities, functions, or non-autogenerated sections. Unexpected run-time behavior might also occur when you use a third-party library that has dependencies on the upgraded JAR files. If you use only default Pega Platform functionalities without any customizations, the JAR files continue to work correctly without any additional actions.

What steps are required to update the application to be compatible with this change?

If you have any JAR customizations, ensure that you test the upgraded JAR files for compatibility and upgrade impact. The following table lists the upgraded JAR files that might impact your application:

JAR file nameUpgraded version
apache-mime4j-core0.8.3
apache-mime4j-dom0.8.3
commons-codec1.15
commons-collectionons44.4
commons:commons-math33.6.1
commons-compress1.20
commons-lang33.9
fontbox2.0.19
httpclient4.5.12
httpcore4.4.13
httpmime4.5.12
istack-commons-runtime3.0.8
jackson-annotations2.10.3
jackson-core2.10.3
jackson-databind2.10.3
jaxb-runtime2.3.2
java-libpst0.9.3
jcommaner1.78
junrar4.0.0
metadata-extractor2.13
openjson1.0.11
parso2.0.11
pdfbox2.0.19
poi4.1.2
poi-ooxml4.1.2
poi-ooxml-schemas4.1.2
poi-scratchpad4.1.2
slf4j-api1.7.28
xmlbeans3.1.0
xmpcore6.1.10

For more information, refer to the documentation of  your JAR provider.

Text predictions simplify the configuration of text analytics for conversational channels

Valid from Pega Version 8.6

Enable text analytics for your conversational channels, such as email and chatbot, by configuring text predictions that manage the text models for your channels. This new type of prediction in Prediction Studio consolidates the AI for analyzing the messages in your conversational channels in one place and replaces the text analyzer rule in Dev Studio.

Through text predictions, you can efficiently configure the outcomes that you want to predict by analyzing the text in your channels:

  • Topics (ticket booking, subscription cancellation, support request)
  • Sentiments (positive, neutral, negative)
  • Entities (people, organizations, airport codes)
  • Languages

You can train and build the models that predict these outcomes through an intuitive process, and then monitor the outcomes through user-friendly charts.

For more information, see Predict customer needs and behaviors by using text predictions in your conversational channels.

Upgrade impact

Channels that you configured with text analyzers in the previous version of your system continue to work in the same manner after the upgrade to the current version. When you edit and save the configuration of an existing channel, the text analyzer rule is automatically upgraded to a text prediction. The associated text prediction is now an object where you can manage and monitor the text analytics for your channel. When you create a new channel in the upgraded system, the system automatically creates a text prediction for that channel.

What steps are required to update the application to be compatible with this change?

  1. Enable the asynchronous model building and reporting in text predictions through job schedulers that use the System Runtime Context (SRC) by adding your application to the SRC.
    For more information, see Automating the runtime context management of background processes.
  2. Enable model building in text predictions by configuring background processing nodes.
    For more information, see Assigning decision management node types to Pega Platform nodes.

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