Harness settings container format includes option for no markup
Valid from Pega Version 7.2.1
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
Valid from Pega Version 7.2.1
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
Valid from Pega Version 7.2.1
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
Valid from Pega Version 7.2.1
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.
Cannot send mobile push notifications when the Pega 7 Platform is hosted on WebSphere Application Server
Valid from Pega Version 7.2.1
Push notifications are not sent to Android or iOS mobile apps when the Pega 7 Platform is hosted on WebSphere Application Server.
More efficient load management strategies for large data pages
Valid from Pega Version 7.2.2
The processing of large data pages on the Pega 7 Platform server during the packaging of offline apps is now faster and much more memory-efficient, especially in environments with many concurrent users. Server communication with the data source is now also optimized by reducing the number of data transfers to only what is needed. In addition, all types of refresh strategies are supported for large data pages.
For more information, see Tutorial: How to use large data pages to store large reference data in offline mobile apps.
New Mobile Apps form for defining and building mobile apps
Valid from Pega Version 7.2.2
You now create and build mobile apps from the Mobile Apps form instead of from the Mobile tab of the Application rule form. The new console is a control center for mobile apps where you can gather applications, services, components, and settings in one place to fully customize your apps in the Pega 7 Platform. You can create and build one instance of a custom mobile app and define multiple native mobile apps that can use the Pega Mobile SDK. To push notifications to an Android or to an iOS device, you must define an SDK mobile app in the Pega 7 Platform with a certificate set that has push notifications enabled.
For more information, see Configuring a custom mobile app and Configuring push notifications for an SDK app.
Build consistent, high-quality sections with design templates
Valid from Pega Version 7.2.2
The Pega 7 Platform provides predefined design templates that you can apply to your sections. Templates eliminate the need to design or copy another layout each time you want to design a section. You also can create custom design templates that can be shared with other users. Custom templates can contain regions (dynamic layouts) that you can further customize for each section.
For more information, see Designing sections by using design templates.
Caching of common rules in offline mobile apps
Valid from Pega Version 7.2.2
To help start offline-enabled mobile apps more quickly from the time when the server was started, you can now cache common Pega 7 Platform rules, including node scope data pages. Optionally, you can also either cache all node scope data pages, with the exception of the selected ones, or cache only the node scope data pages that are explicitly specified. You set up the offline caching options for your custom mobile app in the Advanced tab of the Access Group rule form.
For more information, see the Offline Configuration section in Access Group form - Completing the Advanced tab.
Improved scrollable layouts in a new harness
Valid from Pega Version 7.2.2
By default, you can now create a new harness with a screen layout instead of as a container with a cell structure. This change ensures that you can create an application layout more efficiently; for example, you can specify a scroll area exactly the way you want in a desktop application or a mobile app. You can arrange the header, footer, and main area content at the new harness level by using sections. For example, you can specify headers and footers to be fixed or to scroll with the page. New layout options are configurable in the skin. Different layout selections are available when you use the harness as an app view, a main area, inner harness, or a page view.
For more information, see Configuring a screen layout.