Pega Platform™ now provides text analytics APIs that separate Intelligent Virtual Assistant and text analyzers into independent modules. This solution prevents integration issues when you change your text analyzer configuration.
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.
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.
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.
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.
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.
Improve the performance of your proposition filters by testing them against simulated audiences. You can check how many potential offers are being filtered by each condition of the filter, and discover if a particular criterion is too broad or too narrow for your requirements.
To ensure the best user experience in chat sessions with a Pega Intelligent Virtual Assistant™ (IVA), customer service representatives (CSRs) can now step in and take control of a chat session multiple times, when the chatbot is not capable of correctly answering the user. After the user problem is resolved, the CSR can seamlessly switch control of the chat session back to the chatbot.
Valid from Pega Version 8.4
The condition builder now uses the Anypicker control to categorize the entities, such as fields or when conditions, that your application compares at run time. As a result, you can create conditions in a simplified and accelerated way. You can also select fields that are up to four levels deep within field groups.
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.