Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade
Valid from Pega Version 7.3
If you used node classification in Pega® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type. Agent schedules for standard Pega Platform agents are deleted and re-created with the new node type name, but any customization that you made in Pega 7.2.2 is not saved. You must manually update the agent schedules for standard Pega Platform agents in Pega 7.3.
For more information, see Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3 and the appropriate Deployment Guide.
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.
External keystore support in Pega Platform
Valid from Pega Version 7.3
Pega® Platform now provides the ability to source certificates and encryption keys from external keystores. You use the Keystore rule to specify alternatives to the platform's database to source certificates and keys. You can choose to use a data page, a URL, or an external file in one of the following standard formats: JKS, JWK, PKCS12, KEYTAB, or KEY. Keystore information is stored in cache memory only. It is not stored on the clipboard nor is it directly accessible to the application logic.
For more information, see Creating a Keystore data instance.
Send event notifications in Pega Platform
Valid from Pega Version 7.3
You can configure applications to notify users of case changes or other significant events that occur in an application. Use notifications to engage application users by providing key updates that might be of interest to them.
You can deliver notifications over the default web gadget and email channels or use a custom channel that you created. You can configure multiple web gadgets to display different kinds of notifications. The email channel supports notification frequency of instant, daily, or weekly.
Application users can set their own notification preferences in the run-time portals or override the set preferences for a specific case type instance.
For more information, see Sending event notifications and Management of user notification preferences.
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.
Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3
Valid from Pega Version 7.3
If you used node classification in Pega® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type.
- UniversalNode becomes Universal
- WebUserNode becomes WebUser
- BackgroundProcessingNode becomes BackgroundProcessing
- BIXNode becomes BIX
- SearchNode becomes Search
If you created agents in Pega 7.2.2, agent schedules are also automatically updated with a new name during the upgrade. For more information, see Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade and the appropriate Deployment Guide.
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 OAuth 2.0 authorization in Pega Platform REST services
Valid from Pega Version 7.3
Pega® Platform REST services now support OAuth 2.0 authorization that uses federated authentication with SAML 2.0-compliant identity providers (IDPs). The OAuth 2.0-based authorization can be configured to use the SAML2-bearer grant type with a SAML token profile. This configuration is used when a resource requestor is authenticated by using a SAML2.0-compliant IDP.
For more information, see Security rules and data.
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.