DCO
Valid from Pega Version 7.1.4
This release focused on improving the user experience of creating new rules and tightening up the use of specifications in the Case Designer. The layout of the New and Save As forms were made more intuitive and intelligent. Specification actions were made to be more consistent across various aspects of the Case Designer.
- After removing specification references, users can create and save a new specification.
- Developers may now choose either an existing specification or create a new one for subflows and Split-For-Each shapes.
- If a specification is not associated with flow shapes such as sub flows, Utilities, or Split-For-Each, it is possible to import speciications with the same names, and the flow shapes will default to using those imported specs.
- In the outline view, specification changes will be preserved when switching from tab to tab.
- The View Full Details functionality from either Configure Step or the Outline View will display all details, including the specification requirement links.
Decision Management
Valid from Pega Version 7.1.4
This release contains a number of fixes that improve the configuration and execution of Batch decisions – specifically, a number of usability improvements and addresses some issues when creating strategies on IE8.
- Batch Decision functionality has been enhanced in the NBAM environment.
- In NBAM, users can run the strategy execution batch based on the Seed list class instead of the customer class.
- Interaction data will now work even if Action or Organization dimensions do not have values set.
- Running a strategy which includes a Data Import of a structured page reference will work in batch mode.
- Security was enhanced on the VBD Planner.
- The Access of Role to Object rules have been enhanced to allow users to create new Dimension Operator records.
- The NBAM Segment On Canvas will now fetch the SegMap data, even when the generated extended segment class has not been added to the Pages and Classes of the strategy. The SegMap property will (if it exists) be added to a list of properties to fetch, even if the strategy indicates that it is not used.
- When a strategy is defined on a customer class, users may now specify the list of required properties to fetch for the input definition.
- When creating a new strategy, there is now a section to add a Strategy Results class like Business Issue or Group.