Use multiple built-on applications to enhance ruleset reuse
Valid from Pega Version 7.2
Applications can now have multiple built-on applications, allowing rules to be reused as a part of a built-on application at run time while being developed independently at design time.
Previously, applications built in Pega 7.1 and earlier versions were assembled in a single linear application stack--one application built on top of another application, and so on. Attempting to reuse rulesets and frameworks across applications resulted in having to splice applications together, creating challenges when attempting to support the use of these custom created applications. Starting in Pega 7.2, applications are built on to other applications by using a hierarchical tree structure, and the Pega 7 Platform automatically converts this tree into a linear application stack.
For more information, see Using multiple built-on applications and the Ruleset behavior at design time section in Application stack hierarchy for multiple built-on applications.
Stage-based revision and change request management enhancements
Valid from Pega Version 7.2
The revision and change request processes are based on the case management capabilities provided by the Pega 7 Platform. The customizable flows that controlled the behavior of the revision and change request management (pyManageRevision, pyManageChangeSet, pyApproveChangeSet, and pyDirectDeployment) are now part of the Revision and Change Request case types that govern the behavior of revision management. The change from flow-based to stage-based revision management makes the process more transparent and easier to modify.
For more information, see Stage-based revision and change request management.
Support for delegating map values, correspondence rules, and circumstances
Valid from Pega Version 7.2
You can now delegate map values and correspondence rules from the menu. In addition, you can delegate circumstanced types of the following supported rules and data types:
- Map values
- Correspondence rules
- Paragraphs
- Decision tables
- Data types
Help now available for the Predictive Analytics Director (PAD) portal
Valid from Pega Version 7.2
Help topics for Predictive Analytics Director (PAD) are now available. The comprehensive PAD documentation helps you to understand how to develop and create predictive models that you can combine with other components in Decision Strategy Manager (DSM).
For more information, see Predictive Analytics Director (PAD) and Improvements to the Predictive Analytics Director (PAD) portal.
Offline support for mobile applications
Valid from Pega Version 7.2
You can work on assignments and create cases while your mobile device is offline. By enabling offline support for a case type, you can move cases closer to resolution while your application is disconnected from the network.
For more information, see Enabling offline for support for a case type.
Relevant records to define reusable assets
Valid from Pega Version 7.2
Relevant records describe the collection of rules that refine the behavior, presentation, and definition of a case or data type. They are commonly used to designate records from an inherited class as important or reusable in a child class.
Use relevant records to define information displayed in certain Pega 7 Platform application screens and fields. The Pega 7 Platform provides a number of items marked as relevant records, and you can further manage relevant records for your own case and data types.
For more information, see Relevant records.
Current parameter page can now be passed into activities, collections, and data transforms
Valid from Pega Version 7.2
In collection rules, you can now pass the current parameter page into an activity, data transform, or another collection when you call the activity, data transform, or collection from either a primary or a response action instead of setting up parameters before you call one of these types of rules. The Pass current parameter page check box is now supported on the Collection rule form.
For more information, see Rules and methods supported by a collection.
Improvements to Visual Business Director (VBD)
Valid from Pega Version 7.2
Business monitoring and reporting no longer depends on the external Visual Business Director service because VBD is now embedded in the Pega 7 Platform. You add a VBD node to the cluster to access VBD for simulations and monitoring. In addition, when you use the Google Chrome browser, VBD launches as a new HTML client that provides the visualization.
For more information, see The Visual Business Director (VBD) HTML client and Accessing Visual Business Director (VBD).
New Proposition Filter rule
Valid from Pega Version 7.2
Instances of the Proposition Filter rule allow you to define the validity, eligibility, and relevancy criteria for a set of strategy results. Proposition Filter rules improve performance of filtering propositions that are based on proposition data and customer properties. Proposition filters give more testing and debugging capabilities by offering explanation properties. They are referenced in strategies through the Filter component.
For more information, see About Proposition Filter rules and Strategy components - Arbitration.
New Text Analytics landing page
Valid from Pega Version 7.2
The landing page allows you to create the sentiment and classification text analysis models using a wizard. The wizard allows you to upload training data, train a model using different algorithms, analyze the accuracy of the model, and export the model. You can also create a binary rule file that contains the model and upload it as part of taxonomy or sentiment decision data.
For more information, see Text analytics functionality enhancements.