Published Release Notes

Auto-complete functionality optimized for mobile applications

When typing within a field in a mobile application, once a specified minimum number of search characters is entered, auto-complete functionality (pxAutoComplete) populates the entire screen with a list of suggestions. Tap an item in the list to select it for the specified field, or continue typing to ignore the suggestions.

This feature is only available for mobile applications running in Pega 7.1.7. Any previously created applications can utilize this auto-complete functionality if they are upgraded to run in Pega 7.1.7.

Start typing and auto-complete displays a list of suggested results

Device preview includes a configurable list of common mobile devices

Pega Express device preview displays your application in a simulated mobile device. By previewing your application, you can view the user experience on a desktop, tablet, or phone. You can select from a list of common devices or add devices to the list by editing Pega-DevicePreview-Device.

For more information, see Previewing an application on a mobile device.

Ignore browser and operator locale to display Designer Studio in English

The operator preferences configuration includes the option to ignore the browser and operator locale. Some rulesets are shared between Designer Studio and end-user portals. Translated words might occasionally display in Designer Studio. Selecting the Ignore locale check box ignores the locale of the operator and browser to display Designer Studio portals in U.S. English only.

For more information, see Updating Designer Studio preferences.

Ignore locale settings requires refresh after server restarts

The Ignore locale check box in operator preferences is selected to display Designer Studio in U.S. English. After a server restarts, screens initially ignore this setting. When the screen is refreshed or reopened, the screen is rendered as expected.

Flexbox layout mode for dynamic layouts

The flexbox layout mode is available for dynamic layouts and is now the default layout mode for newly created dynamic layouts. In a flexbox layout, sections contained within the layout can grow or shrink to fit the available space, providing a more efficient way to distribute space between items in a container. Existing dynamic layouts can be converted to the flexbox layout mode. You can configure the layout mode on the Presentation tab of the Dynamic Layout property panel.

For more information, see Dynamic Layout Properties — Presentation tab.

Harness settings container format includes option for no markup

The harness container format includes a No markup option. This option removes the non-semantic table tags from the container header, making it more consistent with current UX best practices. The No markup option is required for the new flexbox-based dynamic layouts to work correctly in Internet Explorer 11.

For more information, see Harness form — Adding a container.

Field value inspector in Live UI

Easily identify and translate field values with the field value inspector. You can also use the field value inspector to validate translations and update missing or incorrect translations. The field value inspector is on the Localize tab of Live UI.

For more information, see Field Value Inspector.

Categorize repeating dynamic layouts

Rows of a repeating dynamic layout can be categorized by a property. Categorization is useful for creating date-based navigation or categorizing list items. You can also set the maximum height of a repeating dynamic layout in the Presentation tab of the repeating dynamic layout properties. You configure categorization on the Operations tab of the repeating dynamic layout.

For more information see Repeating dynamic layout - Operations tab.

Flexbox-based dynamic layouts not supported for Android 4.4 and earlier

Flexbox-based dynamic layouts are not supported in Android 4.4 and earlier. When developing applications to be used on devices running Android 4.4 and earlier, use the inline-block layout mode for dynamic layouts.

Unit testing support for more rule types

You can now create unit tests for the following additional rule types. You can also create assertions to validate activity status. The expanded rule types for unit testing enable developers to more thoroughly perform regression testing of their application, thereby improving application quality.

• Collection
• Declare expression
• Map value
• Report definition

For more information about unit testing rules, see Pega unit test cases.

Upgrade impact

With the four new rule types, unit test execution and unit test compliance metrics will change. Reports on automated unit testing of the customer application decrease due to the increased pool of supported rules.

What steps are required to update the application to be compatible with this change?

After a successful upgrade, create Pega unit test cases for the newly supported rules to see updated and accurate unit test metrics.