Data Flow service in the Pega 7 Platform
Valid from Pega Version 7.2.1
The Data Flow service configuration on the Services landing page now provides a single point of entry for enabling running data flows in batch and real-time modes. To configure the Data Flow service, you must add Decision data nodes on which to run data flows and specify the number of Pega 7 Platform threads that are assigned to process the data flow runs. Additionally, as part of the Data Flow service, you can view the number of active data flows on each node.
For more information, see Services landing page.
MBeans deprecated in favor of Pega API
Valid from Pega Version 8.1
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.
Improved Pega 7 Platform upgrade and update time
Valid from Pega Version 7.2.1
The Pega 7 Platform upgrade and update tools have been improved to streamline indexing. Upgrading and updating are faster than with previous releases.
Adaptive Decision Manager service in the Pega 7 Platform
Valid from Pega Version 7.2.1
The Adaptive Decision Management (ADM) service is now native to the Pega 7 Platform and is supported by the Decision data node infrastructure. Because of this enhancement, you no longer need to manage the ADM service as an external service. In addition, the ADM service does not require dedicated hardware or operating system environments.
For more information, see Services landing page.
Pega Survey documentation refers to deprecated field
Valid from Pega Version 7.2.1
The documentation for Pega® Survey refers to the Answer Layout field on the Complex Question form, but this field is no longer supported. For more information about the question layout formats that Pega Survey supports, see Pega Survey.
Support for multiple custom mobile apps for a Pega Platform application
Valid from Pega Version 8.1
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.
Open cases in a mobile app with push notifications sent from Pega 7 Platform applications
Valid from Pega Version 7.2.1
Push notification smart shapes in a workflow of a Pega 7 Platform application can now send push notifications that open a case in a custom mobile app. Users working in the field can use this feature to instantly access priority assignments instead of having to search for changes manually.
For more information, see Configuring the Push Notification shape.
Cannot send mobile push notifications when the Pega 7 Platform is hosted on WebSphere Application Server
Valid from Pega Version 7.2.1
Push notifications are not sent to Android or iOS mobile apps when the Pega 7 Platform is hosted on WebSphere Application Server.
Search indexes require rebuilding after upgrading from Pega Platform 7.1.7 through 7.2.1
Valid from Pega Version 8.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.
Support for an external Elasticsearch cluster for on-premises deployments
Valid from Pega Version 8.1
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.