Responsive layout groups and grids
Valid from Pega Version 7.1.4
The Responsive UI was introduced in Version 7.1, and has now been enhanced in two areas, to create an entirely responsive UI.
PRPC 7.1.4 introduces the Layout Group control, which can render its contents as “tabs,” “accordions,” or as a “menu.” The rendering choice is driven through the presentation layout (the skin), which presents the information responsively: a “tab” at a certain breakpoint can turn into an “accordion” or a dropdown-style menu, depending upon what format would be most appropriate for the device/screen size being used.
The grid functionality has also been enhanced, so that grids may be displayed on a tablet or a phone without the need for horizontal scrolling, offering the optimum experience on a mobile device. A PRPC Grid Layout now supports responsive breakpoints in the skin definition in which columns can drop off or be consolidated according to screen size.
Designers will be able to mark columns in the grid by importance, and at the first breakpoint, the columns marked as “less important” will be dropped off first. At the second breakpoint, the grid turns into a “fat list,” with the most important column displaying as a heading for each item in the “fat list.” Styling options can be associated with these breakpoints.
Actionable layouts improve mobile experience
Valid from Pega Version 7.1.7
Interactive layouts are now easier to use from a mobile device. With the added ability to specify events and actions on dynamic layouts rather than on individual items, you can deliver enhanced user interface interaction from a mobile device. For example, you can configure interaction with an entire tile rather than individual elements of the tile for easier tapping.
Configure an entire tile for easier interaction from a mobile device
From the Actions tab of the Dynamic layout properties panel, you can define an action set and then add events and actions. Actions on nested layouts or controls take precedence when acted upon.
Specify events and actions from the Actions tab of the properties panel
Mobile tab UI updates
Valid from Pega Version 7.1.7
The Mobile tab (formerly the Mobile Settings tab) on the Application Definition in Designer Studio includes an updated UI and enhanced functionality in this release. This includes:
- When using the default options on the Mobile tab, URLs and QR codes display that link to the Pega 7 mobile application download page on the Apple iTunes and Google Play app stores, providing easier direct access to this app.
- Push notifications can be enabled and configured for both iOS and Android hybrid mobile applications (previously, only iOS apps could use this feature).
Configure push notifications for a hybrid mobile application using the updated fields on the Mobile tab - Warning messages display when building a hybrid mobile application to assist users if any incorrect or incomplete information is entered into a required field.
An example of an error message
For more information, see PDN article How to build and brand a hybrid mobile application.
Addition of Servlet Management
Valid from Pega Version 8.6
Pega Platform™ now has Servlet Management in Pega Cloud® Services, which provides a simple and secure way to make changes to Pega Platform servlet definitions.
Servlet Management provides Pega Cloud Service clients with solutions to manage servlet configurations with self-service options. This reduces the cycle time for delivering configuration changes in Pega Cloud Service installations while also improving upgrade reliability.
For more information, see Servlet management.
Upgrade impact
Clients with no application servlet customizations will not experience an impact. If you upgrade from Pega Platform version 8.5 or earlier and, prior to the upgrade, the Pega Cloud team provided your application servlet customizations, then following the upgrade, you must manually add, remove, or modify your servlet customizations in your upgraded application using this servlet management landing page in Pega Platform.
What steps are required to update the application to be compatible with this change?
To manually move your pre-upgrade servlet customizations as appropriate or add new ones to your upgraded application using the new servlet management landing page, follow the steps in Adding a servlet.