Published Release Notes

UI Kit for building and customizing UI

The UI Kit ruleset (UI-Kit-7) contains rules and skin for building or customizing user interfaces with the latest standard Pega UI, designed to ensure a responsive mobile-friendly UI.

By default, Application Express adds this ruleset to new applications built on the PegaRULES application. To use this ruleset in existing applications, or any applications built on a framework, add it to the Application ruleset list on your application form's Definition tab. Updating the UI Kit with the latest version allows you to take advantage of the latest features and styling. At the same time, this delivery mechanism of the UI Kit will ensure backward compatibility, providing a non-disruptive upgrade.

The UI Kit is delivered as a locked ruleset, and you can customize the rules by copying them into your application ruleset.

Fixed portal type deprecated

Existing portals configured as fixed still work, but there is no longer an option to create a new fixed portal type.

Set X-UA-Compatible mode on harness

Because Internet Explorer (IE) compatibility mode can adversely affect the standards mode in the Pega 7 UI, harness browser mode settings now expose the X-UA-Compatibility mode on a harness.

In previous versions of PRPC, this setting was hidden behind a when rule.

Pick modal dialog templates

Improved modal templates can be customized and used wherever a modal dialog is launched.

Flexible inputs in strategies

Decision parameters allow business users to influence the decision through flexible inputs that do not require changing strategies. System architects use extension points to configure the data model and user interface supporting decision parameters. Decision parameters are used in strategies, and changes to the values of decision parameters become immediately available without requiring any changes to the strategy.

The rule pxRunDecisionParameters supports the use of decision parameters through activities.

Enable business users to own parts of an enterprise application

Decision Manager functionality allows business users to own parts of an enterprise application within the boundaries defined by IT. PegaDM includes the Pega-DecisionManager ruleset that supports this functionality.

System architects define the boundaries for business users in the Decision Manager portal using revision management and proposition authorization facilities in Designer Studio. Access control is provided through custom roles, which system architects can create based on granular privileges. The Decision Manager portal provides business users with a controlled environment for the workflow, and the activities necessary to address the objectives of a revision.

Predefined inputs when designing and testing strategies

External input settings allow for propagating results to other strategies, providing strategy designers with a mechanism to reuse strategies and test strategies with predefined inputs.

Design segmentation trees in strategies

You can include the traditional segmentation tree pattern in your strategies using the following features:

• Exclusion components to conditionally stop the propagation of decision results.
• Split components to branch the decision results according to the percentage of cases covered by the result.
• The Otherwise label for component connections where one of the outgoing connections has a defined label.

Simplified Adaptive Decision Manager Deployment

The Adaptive Decision Manager (ADM) server relies on automatic detection of the database dialect. This simplifies the number of deployable archives used to set up the ADM service.

Cumulative calculation in strategies

Iteration components provide strategies with a mechanism to perform cumulative calculations.