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.

References to parameters in text control

Valid from Pega Version 8.3

The enhanced Text control now supports referencing the parameters in the Property field, and a more flexible application of the Field Value, that you can now use in the Value field. As a result, you can now use more development options, increase reuse, and more accurately reference specific data.

For more information, see Adding a Text control.

Pagination for repeating dynamic layouts

Valid from Pega Version 8.3

Repeating dynamic layouts now support pagination, so that you can display extensive sets of data in smaller portions. Additionally, you can add custom icons or messages to inform users whether more data is available.

For more information, see "Pagination" in Configuration options for layouts.

Faster starting offline-enabled mobile apps

Valid from Pega Version 8.3

Pega Platform™ and Pega Infinity Mobile Client™ now support access group data prepackaging when you build the executable files for an offline-enabled mobile app. This shortens the time needed to start a mobile app for the first time, because only the data that differs between the package and the current server state is synchronized. The data that is prepackaged comes from the access group cache, and you can decide what access group cache data should be excluded or additionally included in the package.

For more information, see Enabling access group data prepackaging during build.

More action types on the bottom bar

Valid from Pega Version 8.3

Pega Infinity Mobile Client™ now provides more flexible bottom bar configuration with a broader choice of actions, so that your apps can be more useful. For example, users can now create work items, open work items, or log out directly from the bottom bar of a mobile app.

For more information, see Configuring the bottom bar.

Change tracking tab removed from declare expressions

Valid from Pega Version 8.3

To simplify the configuration of a declare expression, the Change tracking tab has been removed from the declare expression rule form. To use the Change tracking tab, on the declare expression rule form, click Actions > Use legacy expression.

For more information, see Supported and unsupported configurations in simplified declare expressions.

Upgrade impact

The declare expression rules have been moved from the pr4_rule table to the new pr4_rule_declare_expression table.

The upgrade can fail if you customize the pr4_rule table, such as increasing the length of an existing column.

After a successful upgrade, the declare expression rule form is simplified and lightweight pages support declare expressions.

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

Read-only data pages by default are lightweight. You could also enable lightweight pages for:

Only simplified declare expressions are supported in lightweight pages. In simplified declare expressions, context-bound rules are not supported. However, a page context could be specified on the New or Save As form of declare expressions. For more information, see Declare Expression rules - Completing the New or Save As form.

Redirectguests mashup configuration has been removed

Valid from Pega Version 8.3

The authentication/redirectguests server configuration and data-pega-redirectguests attribute have been removed and are no longer required when you configure a mashup. This prevents you from needing to maintain multiple nodes to support some use cases that require the configuration value to be true and other uses cases that require the configuration value to be false.

For more information, see Configuring the Mashup channel.

Support for custom database tables in external Cassandra clusters

Valid from Pega Version 8.3

Pega Platform™ now supports a connection to external Cassandra clusters through a dedicated Database Table data set, which reduces the need for data ingestion and export. You can use custom tables that you store in your external Cassandra cluster in data flows for accessing and saving data. You can access your custom data model by mapping the model to a Pega Platform class.

For more information, see Connecting to an external Cassandra database through a Database Table data set.

Data synchronization does not resume after mobile app restart

Valid from Pega Version 8.3

If an offline-enabled mobile app that you build with Pega Infinity Mobile Client is stopped during an initial data synchronization session, the data synchronization does not resume when the mobile app is restarted. Users must not stop the mobile app before initial data synchronization finishes.

For more information about data synchronization, see Offline capability and Guidelines for creating an offline-enabled application.

Enhanced data flow performance monitoring

Valid from Pega Version 8.3

The performance alert log now provides more detailed information about the data flows in your application. You can view performance details for data flows that are currently running and data flow runs that have completed successfully. You can also view a performance summary for data flow runs that are running for too long or have failed.

For more information, see:

Text analytics models editing and versioning

Valid from Pega Version 8.3

Pega Platform™ now supports editing and updating training data for text analytics models.

Pega Platform also supports the versioning of text analytics models. When you update the model, Prediction Studio creates an updated model version. You can then switch between the model versions.

Upgrade impact

In versions of Pega Platform earlier than 8.3, the training data for text models was stored in the database. In Pega Platform version 8.3 and later, the training data for text models is stored in Pega Repository. You cannot build new models without setting the repository. After the repository is set, all text models are automatically upgraded and will work normally.

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

After a successful upgrade, set the repository in Prediction Studio before building or updating any Natural Language Processing (NLP) models.  In Prediction Studio, click Settings > Text Model Data Repository.

 

For more information, see:

 

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