Optimized performance of embedded decision strategies
Valid from Pega Version 8.4
The performance of embedded strategies has now been optimized so that these strategies take less time and fewer CPU and memory resources to complete. This enhancement increases the performance of cloud and on-premises deployments.
For more information, see About Strategy rules.
Case notification enhancements
Valid from Pega Version 8.4
Pega Platform™ now supports creating case notifications directly in Case Designer in App Studio and Dev Studio, so that you do not need to create a notification rule first and then provide the rule name in a case. You can speed up and simplify case creation by specifying recipients for each notification, without the need to create a data page for the recipients. Push notifications and email subjects can now also include properties, for example, a case ID or a goal and deadline.
For more information, see Sending event notifications from cases in Dev Studio, Sending event notifications from cases in App Studio.
Improved and simplified field-level auditing
Valid from Pega Version 8.4
To track the progress of your work and maintain the compliance of your cases, both App Studio and Dev Studio now support field-level auditing for case fields. Your application tracks and displays information about user updates to scalar fields, field groups, and field group lists, at any level of your case data model. For example, you can check previous and current field values, the last user to change the values, and the time of their modification.
For more information, see Track changes in cases with improved field-level auditing (8.4), Enabling field-level auditing in Dev Studio, Enabling field-level auditing in App Studio.
Creation of case documents in a case life cycle
Valid from Pega Version 8.4
To save time and further automate your business processes, Pega Platform™ now supports generating case documents as part of the case life cycle. You can ensure that the documents include all necessary information by first creating a document template in a word processor. When you create a template, you add dynamic tags that your application populates with relevant data unique to each case, for example, the case ID and current date. To make your documentation more meaningful, you can also include attachments.
For more information, see Generate case documents in a case life cycle (8.4), Generating case documents in Dev Studio, Generating case documents in App Studio.
New method of aggregating real-time events
Valid from Pega Version 8.4
Event Strategy now uses the approximate median for calculating aggregations. Approximate median calculation replaces the existing method because it requires fewer system resources for saving or loading the event strategy state. In addition, you can now calculate aggregated values by using a new Landmark window type. The window type captures all values of specific event properties from the start of the data flow that references the event strategy.
For more information, see Adding aggregations in event strategies.
Pulse configurations in the case type settings
Valid from Pega Version 8.4
In both App Studio and Dev Studio you can now configure Pulse in a simplified and user-friendly way, in the case type settings. Add Pulse posts to cases, define default and add new feed sources, and then customize the Pulse label, all without performing advanced actions, such as configuring sections. You can also define visibility conditions for each post type.
For more information, see Start collaborating faster with simplified Pulse configuration (8.4), Configuring Pulse for case types in Dev Studio, Configuring Pulse for case types in App Studio.
Extended language support in text analytics
Valid from Pega Version 8.4
Pega Platform™ text analytics now supports 9 more languages. You can build entity and topic detection models to analyze text in the Japanese, Russian, Turkish, Danish, Norwegian, Swedish, Polish, Croatian, and Czech languages. In addition, Pega Platform now includes a default small talk detection model for each of these languages.
For more information, see Language support for NLP and Out-of-the-box text analytics models.
Historical data extraction for adaptive models
Valid from Pega Version 8.4
Adaptive models now support the extraction of historical customer responses for offline analysis. Additionally, you can use the historical data to build a model in a machine learning service of your choice.
For more information, see Extract historical responses from adaptive models for offline analysis (8.4).
Improved reliability of Visual Business Director
Valid from Pega Version 8.4
Improvements to the reliability of Visual Business Director (VBD) eliminate the impact of temporary access loss to the VBD cluster. The improvements include the ability to continue writing data to a VBD dataset while the corresponding server node is unavailable, enhancements to single-case data flows that write data to VBD, and a reduction in the VBD cache size.
For more information, see Eliminate the impact of temporary access loss to the VBD cluster (8.4).
Strategies are now available as a condition type in proposition filters
Valid from Pega Version 8.4
When designing proposition filters, you can now include strategy outcomes as a condition to be evaluated. Select a strategy and specify the component that you want to use as output to include more advanced decisioning in your proposition filters.
For more information, see Enrich your Proposition Filter rules with conditions based on strategy results.