Published Release Notes

Clustering equal to none might cause errors

Some Pega 7 Platform features might not work when theidentification/cluster/protocolsetting in the prconfig.xml file is set to none. Some features that might not work are remote tracing and management actions on the node from the Requestor Management and Agent Management landing pages. Setting the clustering protocol to none is not recommended and will not be supported in a future Pega 7 Platform release.

Search reindexing is automatically triggered

Reindexing on index host nodes is now triggered automatically when no other index node exists in the cluster, eliminating the need for you to manually clean up old items and start reindexing. In addition, offline index host nodes are removed as index host nodes during normal shutdown and startup of any node in the cluster. As a result, you might have to add back a node as an index host node on the Search landing page. You can configure a node to always be an index host node or to never be an index host node by using the JVM -Dindex.directory option as described in Managing Elasticsearch index host nodes outside of the Search landing page.

You can turn off automatic reindexing by using the indexing/distributed/automodecleanupandreindex Dynamic System Setting.

Node classification feature

With the node classification feature, you can group production nodes by different node types to segregate nodes by their purpose. Currently, agents and listeners can be associated with node types. If you start a node with a specific node type, the node runs only the associated agents and listeners for that node type. This enhancement improves performance and optimizes resources.

For more information, see Configuring node types for agents and listeners, Mapping listeners to node types, and Mapping agents to node types.

Default quiesce strategy changed to immediate drain

The default quiesce strategy has been changed to immediate drain, which allows you to continue to access a quiescing node to perform actions until the node is removed from the load balancer, regardless of your user role. When immediate drain is enabled, and a node is in the quiesce state, the requestor state is saved after every interaction. After the node has been removed from the load balancer, the saved state can be used to restore the requestor state on a new node in the next interaction with the server.

You can change the quiesce strategy default to slow drain by modifying the value of the session/ha/quiesce/strategy setting in the prconfig.xml file to be slowDrain.

New Mobile Apps form for defining and building mobile apps

You now create and build mobile apps in Pega Express from the Mobile Apps form. The new console is a control center for mobile apps where you can gather applications, services, components, and settings in one place to fully customize your apps. You can create and build one instance of a custom mobile app and define multiple native mobile apps that can use the Pega Mobile SDK. To push notifications to an Android or to an iOS device, you must define an SDK mobile app in Pega Express with a certificate set that has push notifications enabled.

For more information, see Configuring a custom mobile app and Configuring push notifications for an SDK app.

Navigation of sections based on templates in Pega Express

When editing a case form in Pega Express, you can navigate up and down through the section structure. If a section uses a design template, you can drill down to a nested child section by clicking it. Drilling down facilitates navigation through the section structure. You can drill down from a parent to a child section or up from a child section to its parent.

For more information, see Improved section navigation and organization in Pega Express.

Drag and drop sections in Pega Express

When editing a case form, you can select, drag, and drop sections that use a design template inside a form. Drag and drop provides a simplified way to reorganize sections on a form.

For more information, see Improved section navigation and organization in Pega Express.

Automated Unit Testing (AUT) content removed from the help

Information about Automated Unit Testing (AUT) has been removed from the Pega 7 Platform help, beginning with version 7.2.2. The AUT information is still available in earlier versions of the Pega 7 Platform help and on the PDN in the topic category Testing Applications.

PegaUnit testing is now supported on data pages, activities, data transforms, strategies, decision tables, and decision trees, which you can use to quickly and easily create test cases for your Pega 7 Platform applications instead of using AUT.

For more information, see:

• Pega 7.2.2 behavior when switching between PegaUnit testing and Automated Unit Testing features
• Automated Unit Testing

Push real-time notifications to your clients

You can now set up a real-time notification system based on the publish/subscribe (pub/sub) messaging pattern where a node in the cluster can push notifications to your browser clients. Nodes publish notifications to a channel that can broadcast to all the subscribed browser clients.

You can create a notification channel from the Notification channels landing page and subscribe to the channel by selecting the On Load action, which is available under action sets.

For more information, see Real-time applications and push notifications in the Pega 7 Platform.

Disregard this startup error for Oracle Weblogic deployments

If you install, upgrade, or update your Oracle Weblogic application server to Pega 7.2.2, disregard the error stack that begins with text similar to the following:

ERROR - WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014 1604337 Oracle WebLogic Server Module Dependencies 12.1 Tue Mar 11 15:35:15 MDT 2014 WebLogic Jersey Server Integration 3.0 Fri Feb 21 10:55:11 UTC 2014 must use JDK 1.8+ with WebSocket
2016-11-07 06:13:01,690 [ WIN-L3EEURCNCP1] [ STANDARD] (pr.DefaultAsyncSupportResolver) ERROR - Real error: Unable to configure jsr356 at that stage. ServerContainer is null

This message appears because the Pega 7.2.2 real-time notification feature initially tries to use WebSocket and then falls back to long polling. The Pega 7 Platform does not support WebSocket for Oracle Weblogic servers, and instead uses long polling for real-time notifications.