Stage progression in a life cycle includes alternate paths
Valid from Pega Version 7.3
In Pega Express, you can now add alternate stages to the life cycle of a case type. You can also change the type of a stage from primary to alternate, or alternate to primary. By using different types of stages, you can separate expected behavior from the exceptions in your application.
For more information about stages, see Defining a life cycle for a case type.
Support for rule rebasing
Valid from Pega Version 7.3.1
You can now rebase the rules on your development server with the most recently committed rules from a centralized system of record (SOR). For example, after rules are merged on the SOR, you can rebase your development application to refresh your application with the merged rules. Development teams working in two separate development environments can share their changes, keep their local rulebases synchronized, and reduce the probability of conflicts with other development teams.
For more information, see Rule rebasing.
Use definition classes to create Decision Data rules that contain text analytics records
Valid from Pega Version 7.3
Use the dedicated definition classes to create Decision Data rules that contain all the types of records that are used in text analytics, such as taxonomies, lexicon, entity extraction rules, and so on. By using these definition classes, you can quickly create, update, and manage the text analytics records in your application.
For more information, see Definition class of text analytics Decision Data rules.
Actions available for custom controls
Valid from Pega Version 7.3
All standard actions that are available for autogenerated controls are available on non-autogenerated custom controls as well. You can configure actions on custom controls by using the legacy actions options or the standard options that are available to custom and autogenerated controls. By using the standard options, developers can now configure multiple action sets for different types of events on a single custom control.
For more information, see Actions tab.
Push notifications and Oracle WebLogic Server 10.3.6
Valid from Pega Version 7.2.2
Pega® Platform push notifications can use WebSockets and long polling. However, for WebLogic Server 10.3.6, the push notifications feature does not work. To disable the feature, contact Pegasystems Global Customer Support.
Load balancing: HTTPD does not support WebSockets by default
Valid from Pega Version 7.2.2
If you use a load balancer with HTTPD (Hypertext Transfer Protocol Daemon), HTTPD does not support fully functional WebSockets and sticky sessions. By default, HTTPD does not support sticky sessions, because if it did, after a session was started, the same server would serve all requests for that session.
Relevant records now support class inheritance
Valid from Pega Version 7.3
Relevant records can now be inherited through your class hierarchy. For example, a property that is marked as a relevant record at the Work- class can also be inherited by the child classes of the Work- class.
For more information, see Adding relevant records.
Support for conversational user channels
Valid from Pega Version 7.3
You can now communicate with users and customers of a Pega® Platform application by using Pega Intelligent Virtual Assistant acting as a conversational user channel. You can now use Facebook Messenger, Alexa voice commands, standard email, or mobile texting (SMS) to interact with Pega Platform, for example, to open a case or display a menu of available options. In addition, in the Facebook channel configuration, you define text analyzer rules for advanced text analysis, based on artificial intelligence, so that the system provides the best response to users.
For more information, see Intelligent Virtual Assistant.
New Pega0086 alert and enhanced Pega0019 alert
Valid from Pega Version 7.3
The PEGA0086 alert is generated when the maximum number of attempts to acquire a lock on a requestor has been exceeded and a thread fails to obtain a lock on the requestor, and as a result, displays the RequestorLockException message. The Pega0019 alert has been enhanced and now contains additional information such as a user name, an application name, and a thread stack trace, which are associated with the long-running requestor.
For more information, see PEGA0086: Requestor locked by a busy thread and PEGA0019 alert: Long-running requestor detected.
Create resilient data flow runs
Valid from Pega Version 7.3
The resilience of data flow runs has been improved. If Data Flow service nodes fail, active data flow runs continue on the remaining functional nodes. Depending on the type of primary data source and the selected run failure policy, data partitions on the failed nodes can be reprocessed on another functional node or the data flow run is marked as failed for further investigation. You can also add or remove nodes from the Data Flow service while data flow runs are in progress. The runs are automatically rescaled.
For more information, see Data flow run updates.