Published Release Notes

Internet Application Composer mashup code generation

Case types can be added to an external web page by using the mashup code created in Case Designer. The mashup code is custom HTML that can be added to Internet Application Composer (IAC) codes.

The Actions menu in Case Designer includes the ability to automatically generate IAC HTML from a case type. The HTML is then copied and pasted into the target web page through standard IAC options.

The generated code is optimized for responsive web sites and responsive Pega applications. See Generating a mashup code in case configuration.

New context menu in the ruleform header

A new context menu has been added to the Applies To class in the ruleform header. This menu provides the following links that are related to the current rule:

• Show in App Explorer – switches the Application Explorer to the Applies To class of the current rule.
• Open in class record – opens the Applies To class definition.
• View in data designer – opens the Data Designer for the Applies To class.
• View inheritance – opens the inheritance display for the Applies To class.

Edit application elements at run time by using Live UI

Live UI supports the addition, deletion, or reordering of UI elements within the run-time portal. Move elements by dragging and dropping within the tree. Elements can be added, deleted, and moved within or between dynamic layouts at run time by using Live UI.

Merge multiple branches at the same time

Enhancements to the Merge Branches wizard provide support for the merging of multiple branches at the same time. Additionally, the Merge Branches wizard now uses the latest user interface design.

Enhanced Expression Builder

Several enhancements have been made to the Expression Builder. The Expression Builder is displayed in multiple locations and guides you when creating construct arithmetic and logical expressions in your application.

Enhancements to the Expression Builder include:

• An updated text editor
• A navigational pane that displays functions in available libraries and properties within a selected page
• The ability to drag functions and properties into the text editor
• The ability to search for properties and non-internal functions
• The ability to select properties and functions from prompts in the text editor
• Automatic bracket-matching
• Syntax highlighting

Full-screen menus improve mobile navigation

A new full-screen menu setting for enhanced mobile functionality provides a smooth and seamless mobile navigation experience. Previously, regular drop-down menus were difficult to navigate on a mobile device. Select Component styles > Menus > Menu Bar > Display "Show Menu" as full screen menu to enable and configure this setting in a Skin form.

Personalize your dashboard with widgets and templates

New personalized dashboards can be customized and shared by end users. Select a default template or create your own. Choose from one of several default widgets or design a configurable widget to provide core business metrics to your users. From the new Settings tab, you can select whether a section is a template or widget.

Data page automated unit testing

Automated unit testing for data pages now provides a guided way to create and modify automated unit test cases for data pages. Test cases are created by running the data page and converting to a test. Unit tests compare the expected value of a property with the property’s actual value on the data page.

Landing page for data page automated unit test

A new landing page lists all test cases that are associated with the data pages in an application. The landing page includes the data page that corresponds to the test, the data type, and the results of the most recent test case run. A new test case can be created and added from the landing page. Existing test cases can also be run either individually or in batches from the landing page.

Updated Rule-Utility-Function resolution

Rule-Utility-Function rules are now resolved based on ruleset.

Previously, if you had the same function @xyz() in different libraries in different rulesets, you could not call the function by using @xyz, because that would throw an exception.

The resolution process has since been updated so that rule resolution is now based on the highest ruleset in context. This update makes the function resolution process consistent with how rule resolution is performed for other rule types.

For more information, see Functions in expressions.