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.
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.
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.
Performance enhancements to the Strategy rule
Valid from Pega Version 7.3
Strategy designers can create globally optimized strategies to increase the performance of existing strategies. Globally optimized strategies reduce computation time and memory consumption when you run large-scale batch data flows and simulations. Improvements to the Strategy rule performance are the result of decreased run time and quality changes to the code generation model.
For more information, see Introduction of globally optimized strategies.
Define partitioning of stream data sets
Valid from Pega Version 7.3
You can define partition keys for Data Set rules of type Stream to group similar properties and to process Data Flow rules that contain stream data sets more efficiently across multiple Data flow service nodes. Use this feature only for testing in non-production application environments.
Support for Apache Cassandra
Valid from Pega Version 7.3.1
The Pega® Platform can now read data from and write data to an Apache Cassandra database. Apache Cassandra is a NoSQL database that you can use when a NoSQL database better meets your scalability and processing requirements.
For a list of supported and unsupported features, see Apache Cassandra support.
WebSphere log error with Java 8 for Enterprise JavaBeans
Valid from Pega Version 7.1.8
For environments that are deployed by using Java 8 on IBM WebSphere Application Server version 8.5.5.9 through the last 8.5.5.x fix pack, the log might report that a class was not found when the application server attempts to start Enterprise JavaBeans. If Java EE functionality is not needed, no further action is required. However, to use Enterprise JavaBeans, see WebSphere log error with Java 8 for Enterprise JavaBeans.
Create specialized Decision Data rules for text analytics resources
Valid from Pega Version 7.3
You can store various types of resources for text analytics in Decision Data rules that are based on templates. Each resource type (for example, sentiment analysis models, taxonomies, entity extraction rules, and so on) has its own definition class that defines the appearance of the corresponding Decision Data rule form. With this enhancement, system architects can create and maintain various text analytics-related artifacts without having to edit the default Decision Data form fields first.
For more information, see Definition class of text analytics Decision Data rules.