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.

Ability to support advanced device features with Pega Infinity Mobile Client

Valid from Pega Version 8.3

Pega Infinity Mobile Client™ now provides a development kit that you can use to make mobile apps support advanced device features that are typically available to native applications, for example, an embedded laser scanner or a projector module, and integrate functions of external software solutions, for example, a cloud-based file storage.

For more information about enhancing mobile apps with device feature support, see the documentation for the development module in the latest Pega Infinity Mobile Client distribution package on Digital Delivery.

Text analytics models migration

Valid from Pega Version 8.3

Pega Platform™ now supports the exporting and importing of text analytics models. For example, you can export a model to a production system so that it can gather feedback data. You can then update the model with the collected feedback data to increase the model's accuracy.

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:

Support for regular performance alerts

Valid from Pega Version 8.3

You can now specify how often Pega Platform™ sends you performance alerts about SLA violations in data flow runs. By default, the interval is 5 seconds for single case data flows and 5 minutes for batch and real-time data flows.

The following dynamic system settings control the alert interval:

  • Single case runs: dataflow/singlecase/alert/throttleTime
  • Batch runs: dataflow/batch/alert/throttleTime
  • Real-time runs: dataflow/realtime/alert/throttleTime

For more information, see PEGA0062 alert: Data flow execution time above threshold.

Automatic model training when mapping entities to case properties in Email Bot

Valid from Pega Version 8.3

You can now initiate automatic feedback to entity models in Pega Email Bot™, during manual mapping of email content to a case property.

To enable automatic feedback, you set the Work-Channel-Triage.pyIsRuntimeFeedback rule to true in Pega Platform™. By default this feature is disabled. Enabling this feature ensures that the email bot is more responsive by automatically copying detected entities, such as names, locations, dates, and ZIP codes, to case type properties of a case type.

For more information, see Email triage, Email channel NLP model and Enabling the NLP model training for the email channel.

Prediction Studio notifications

Valid from Pega Version 8.3

Prediction Studio now displays notifications when adaptive or predictive models encounter problems. For example, if the performance of a model decreases suddenly, a notification appears, which you can use to immediately investigate the cause of the problem.

For more information, see Accessing Prediction Studio notifications and Prediction Studio notification types.

Production data sampling and migration for decision strategy simulations

Valid from Pega Version 8.3

Pega Platform™ now supports the sampling and migration of data from the production environment to the simulation environment. The data that is migrated for simulations includes customer details, Adaptive Decision Management information, and interaction history. By running a simulation on that sample data in Pega Marketing™ or Pega Customer Decision Hub™, you can verify how the changes to your decision logic impact the results. You can use that information to optimize and adjust your decision algorithms and processes.

For more information, see Deploying sample production data to a simulation environment for testing.

Integrate text analytics with decision strategies through the Interaction API

Valid from Pega Version 8.3

The Interaction API provides more context for making next-best-action decisions by integrating text analytics with decision management components such as strategies, propositions, and interaction history. By including natural language processing in your decisioning solution through the Interaction API, you ensure that the next-best-action decisions that you make are more informed and accurate.

For more information, see Customizable Interaction API for text analytics.

BIX ruleset is now included with Pega Platform

Valid from Pega Version 8.3

The Pega Business Intelligence Exchange™ (BIX) ruleset is now included with Pega Platform™, which eliminates the need for additional provisioning for Pega Cloud customers and for a separate BIX installation for on-premises customers. To add BIX to your application, add the Pega-BIX:<version> ruleset to your application rulesets.

For more information, see Data extraction.

Upgrade impact

After a successful upgrade, the BIX ruleset is available within Pega Platform. You should synchronize the BIX ruleset and Pega rules to avoid extraction errors.

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

After the upgrade is complete, change the ruleset version for Pega Platform and BIX to use the same, latest version.

Set a time zone for the DateTime control

Valid from Pega Version 8.3

The DateTime control now supports the selection of a specific time zone. Apart from the default local time zone, you can choose a Java-supported time zone or enter a property. For example, you can make it easier for a manager working in New York to schedule a task for a worker in London by configuring a calendar picker on user forms to show a date and time for Europe/London.

Beginning with this release, the calendar picker defaults to the current time in the time zone that is defined in the operator record. Previously, it defaulted to the local time zone of the system.

For more information, see Specifying a time zone for a DateTime control.

Upgrade impact

After a successful upgrade, the DateTime gadget displays the time in the current operator's locale, which is defined on the operator rule form or in the browser.  

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

If you need to display the system time from which the user has logged in, and if this is not the same as the time in the user's locale (based on the browser setting), set the Locale field in the operator ID to be blank so that the browser-based setting and the displayed time are the same as the system time.

Support for machine learning as a service models

Valid from Pega Version 8.3

In Pega Platform™, you can now run advanced machine learning and artificial intelligence models that you develop in third-party tools. By configuring a connection with an external machine learning as a service provider, such as Google AI Platform, you can use the predictive power of your custom models to improve the predictions in your customer strategies.

For more information, see Connecting to a Machine Learning as a Service model and Configuring a machine learning service connection.

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