Published Release Notes

MBeans deprecated in favor of Pega API

The use of MBeans for cluster management has been deprecated, although MBeans will continue to function for legacy deployments. The recommended best practice for automating system management is to use the Pega API. For more information, see Pega API.

Support for multiple custom mobile apps for a Pega Platform application

To enhance the user experience and provide support for native mobile components, you can create multiple custom mobile apps for a Pega Platform™ application. For each custom mobile app, you must create a different mobile channel interface. In addition, you can configure each custom mobile app to run only in a specific portal for an application. The custom mobile app uses this portal regardless of which default portal is defined for the access group.

For more information, see Selecting a portal for a custom mobile app.

Search indexes require rebuilding after upgrading from Pega Platform 7.1.7 through 7.2.1

Pega Platform™ now supports Elasticsearch 5.6.9. If you are upgrading from Pega 7.1.7 through 7.2.1, discard your existing indexes and build new indexes in a new empty index directory. Create the search indexes by using the Search landing page or the full text indexer. If you are upgrading from Pega Platform 7.2.2 or later, no action is required. You can continue to use your existing search indexes.

For more information, see Rebuilding search indexes and Batch creation and updating of Elasticsearch index files from the command line.

Deprecated rule types

The following rule types have been deprecated as of the Pega 7.1.8 release:

• Form
• Hierarchy
• Service COM
• Service BPEL
• Connect BPEL
• Parse Transform
• Parse Transform Collection
• Parse Infer

For more information, including suggested alternate rule types, see the help topic Deprecated features.

Simplified Adaptive Decision Manager Deployment

The Adaptive Decision Manager (ADM) server relies on automatic detection of the database dialect. This simplifies the number of deployable archives used to set up the ADM service.

Support for an external Elasticsearch cluster for on-premises deployments

On-premises customers can configure an Elasticsearch cluster that is external to the Pega Platform™ by using client-server mode. Using an external search configuration makes Elasticsearch more highly available and scalable. 

You can view the status of your external Elasticsearch service on the Search landing page. For more information, see link to Viewing the status of an external search service.

Ability to deprecate a rule

You can deprecate any Rule- instance to indicate that it is no longer supported.

Users are warned when they open or reference a deprecated rule instance.

Ability to deprecate a class

You can deprecate any Rule- class to block users from creating new rule instances.

Users are warned when they open the class rule form or any instance of the class.

Simplified process for JMS MDB listener deployment

The process for deploying a JMS message-driven bean (MDB) that represents a JMS MDB listener has been streamlined for new enterprise applications. It is now less complicated and can be performed in fewer steps.

For more information on deploying to WebSphere, WebLogic, and JBoss, refer to the PDN article Deploying a JMS message-driven bean (MDB) that represents a JMS MDB listener in Pega 7.

Formally deprecated rule types

The following rule types have been deprecated. Migrate to alternatives as appropriate: