Improved performance of decision strategies
Valid from Pega Version 8.1
Strategy rule performance has been improved through the implementation of a new engine. You can perform single and batch test runs to analyze strategy performance, locate and prevent potential issues, and optimize strategy components. Test runs now support data sets and data flows with multiple key properties. The redesigned Test run panel improves the display of information and highlights the most immediately relevant details.
For more information, see Configuring a single case runs and Configuring a batch case runs.
View mini user profiles in Pulse
Valid from Pega Version 8.1
You can now view mini profiles of users who post messages and users who are referenced in Pulse, by clicking the name of the user. A mini profile contains the user's job title, reporting manager, organization, and links to call and send email to the user. By seeing a brief overview of a user profile, you can access important information about users and contact them more quickly.
For more information about Pulse, see:
- App Studio – Communicating with users by using Pulse
- Dev Studio – Communicating with users by using Pulse
Mashup code preview in App Studio
Valid from Pega Version 8.2
When you create a mashup channel for your application, you can now eliminate issues with the code and create better looking applications, by using the portal preview in App Studio. You can preview a channel to verify that different types of devices correctly display the mashup code. The preview functionality uses a default wrapper that functions as a portal for displaying a frame with the mashup code. You can modify the appearance of the default wrapper, and adapt the mashup user interface in design mode to meet your requirements.
For more information, see Configuring the Mashup channel and Previewing an application.
Facilitated application development with saving changes in branches in App Studio
Valid from Pega Version 8.3
For improved development of your application, you can now define branches in which you save changes that you make to your application in App Studio. Create features in branches so that you can review and merge them without affecting other features in the application. You can quickly identify and review any changes to rules because you know in which application layer they were saved.
For more information, see Setting branch preferences in Dev Studio, Setting branch preferences in App Studio.
Response timeout configuration for predictions
Valid from Pega Version 8.5
You can now set a response timeout for your predictions in Prediction Studio. By setting a response timeout, you control how Prediction Studio registers customer responses that later serve as feedback data for your predictions.
For more information, see Customizing predictions.
Delayed adaptive learning
Valid from Pega Version 7.1.7
Data flows, a new rule type in Pega 7.1.7, allow you to store adaptive inputs and interaction results for a given period of time when running a strategy. This makes it possible to capture and learn from responses at a later date. For more information on data flow design for delayed learning, see Data Flow rule form - Completing the Data Flow tab.
Create and edit reports
Valid from Pega Version 7.2
In Pega Express, you can now create and edit reports for the case types in your application. You can use the new reporting features to modify the way information is displayed in a report and to sort and filter the data for different audiences.
For more information, see Creating reports and Editing reports.
Visual Business Director service renamed to Real Time Data Grid service
Valid from Pega Version 7.3
To avoid confusion in the Pega Marketing application, the Visual Business Director service has been renamed to Real Time Data Grid service.
For more information, see Real Time Data Grid service.
Moderate and severe guardrail warnings require justification
Valid from Pega Version 8.2
When checking in a rule, all moderate and severe warnings must be justified. Guardrail warnings now appear in a warning header when you save a rule that has warnings. Requiring justification encourages developers to address guardrail warnings. For more information see Application guardrails require justification.
Improved contracts for implementations
Valid from Pega Version 8.4
For more complete contracts, automations now support embedded pages, default values, and picklists. These enhancements provide a more robust model for inputs and outputs that is easier to update and maintain.
For more information, see Viewing automations.