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.
New Mobile Apps form for defining and building mobile apps
Valid from Pega Version 7.2.2
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.
Text analytics infrastructure upgraded to Java version 1.7
Valid from Pega Version 7.2.2
The JAR libraries that support the text analytics features of the Pega 7 Platform have been upgraded to Java 1.7. As a result of the upgrade, you can validate the Ruta scripts that contain entity extraction models and view error reports if the imported Ruta scripts are invalid. This upgrade helps you to ensure that the structure of the entity extraction models that you import to your application is always correct.
For more information, see Text Analyzer.
Visual Business Director can be used in HIPAA-regulated environments
Valid from Pega Version 7.2.2
Communication between the Visual Business Director client nodes and the Visual Business Director server nodes now uses PRCluster. This new setup allows Visual Business Director to use the underlying clustering technology instead of depending on third-party solutions.
For more information, see Visual Business Director service.
Pega File Listener process changes
Valid from Pega Version 7.2.2
Beginning with Pega 7.2.2, File Listener processes files in a different way:
- File movement in directories – Previously, files were processed from the Work directory. In Pega 7.2.2, files are processed from the source location. Files move to the Work directory only if the initial processing fails and Recovery is disabled.
- New file processing – Previously, File Listener would process all files in the source location, even if the files were added during the processing. In Pega 7.2.2, files added to the source location during processing are read the next time the File Listener starts.
For more information, see File Listener data instances.
New Decision Strategy Manager alerts
Valid from Pega Version 7.2.2
Autonomic Event Services (AES) is now monitoring new Decision Strategy Manager (DSM) alerts that allow diagnosis of performance-related issues with Decisioning services (Adaptive Decision Manager, Visual Business Director, Data Flow, and Decision Data Store).
For more information, see Performance alerts, security alerts, and AES and Services landing page.