Customizable New Application wizard
Valid from Pega Version 7.2.2
The redesigned New Application wizard streamlines the process of creating and configuring applications, and introduces customizable application templates. When you create an application from an application template, the template defines the wizard steps that gather the information that is needed to configure your new application based on the template. After you specify the required information in the wizard, the system creates an application with the required case types, data types, access groups, and operators. You can create multiple templates, depending on the needs of your business. Sample template types are provided.
For more information, see New Application wizard.
Create case and Wait smart shapes available in Case Designer
Valid from Pega Version 7.2.2
Two smart shapes have been added in Case Designer. Use the Create case smart shape in a case step to create another case, a child case, or multiple child cases. Use the Wait smart shape to pause the process of a case under specified conditions.
For more information, see Adding a preconfigured step to a process.
Search reindexing is automatically triggered
Valid from Pega Version 7.2.2
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
Valid from Pega Version 7.2.2
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.
Include videos within sections
Valid from Pega Version 7.2.2
You can include videos within sections to build an interactive user experience. As with other standard controls, you can configure the video presentation and event properties. Although the Pega 7 Platform supports multiple video types, use the MP4 format as a best practice.
For more information, see Adding a video to a section.
New PEGA0084 alert - Search node count
Valid from Pega Version 7.2.2
The PEGA0084 alert is generated when the number of available index host nodes does not meet the quorum ((replicas/2) + 1) required for index writes to succeed. This alert can occur when some of the index nodes go down, causing the number of available index host nodes to be less than the quorum. For more information, see PEGA0084 - Search node count.
Default quiesce strategy changed to immediate drain
Valid from Pega Version 7.2.2
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.
Data transform support in offline-enabled applications
Valid from Pega Version 7.2.2
You can now use data transforms in offline-enabled applications to reduce the need to write your own custom JavaScript functions. Data transforms are automatically packaged for offline use when they are configured on flow connectors, as preprocessing or postprocessing data transforms on a flow action, or on refresh actions or data transform actions on controls in a section. You also can run a data transform in offline mode by using a Run Script action or a custom JavaScript function, provided you add the data transform definition to the rule of offline-supported data transforms.
For more information, see Data transform support in offline mode.
Use Kerberos credentials in a Pega application to authenticate and access external systems
Valid from Pega Version 7.2.2
Authentication services now support Kerberos as an authentication type. When you connect from the Pega 7 Platform to external systems and services that require Kerberos authentication, the Pega 7 Platform stores the user Kerberos credentials and makes them available in Pega 7 Platform connectors.
For more information, see Using Kerberos credentials in a Pega application to authenticate and access external systems.
A new transition effect for actions in custom mobile apps
Valid from Pega Version 7.2.2
Custom mobile apps that are developed on the Pega 7 Platform can include a new transition effect that animates your navigation in cases that use flows. This feature adds to the look-and-feel experience of the custom mobile app.
You can also add the pega.mobile.transitions.GO_HOME transition effect to actions that do not support built-in effects by using the Run Script action and calling the pega.desktop.setNativeTransition() JavaScript method.
For more information, see Transition effects on actions.