Published Release Notes

Drag-and-drop functionality for lists and tables

Lists and optimized tables now support the reorganization of their content by reordering items. By configuring repeating dynamic layouts and tables to support drag-and-drop modifications, you enable users to move items between lists and within lists and tables. This enhancement ensures that you can create a flexible and dynamic user interface that helps users display and manage data.

The drag-and-drop functionality can also include custom actions that automate the processes that run when users move items.

For more information, see Configuring drag-and-drop functionality for lists and Configuring drag-and-drop functionality for tables.

Usability improvements to Admin Studio

Admin Studio offers a variety of usability enhancements, including:

• New access groups to differentiate between full and read-only access to Admin Studio
• A Java class lookup utility
• A requestor list for the logged-on operator
• The ability to display system node type in the logs

Also, if your environment uses Predictive Diagnostic Cloud (PDC), the Admin Studio overview page now includes a link to PDC.

For more information, see Managing requestors.

Table toolbar functions

Optimized tables now support a table toolbar, that provides application users with the ability to adjust the data display to their needs. The toolbar conveniently groups several standard functions and custom actions. By using the toolbar, users can change the visibility of columns, group table data by fields, adjust the height of rows, and then save their personalized view. The toolbar is generated automatically, which provides a consistent design throughout your application.

For more information, see Configuring the table toolbar.

Role-based page access in App Studio

App Studio now supports the management of access to pages in your application based on user roles. You can use this functionality to define which pages are visible for every role, for example, make an analytics page available only to an administrator.

For more information, see Configuring role-based page access.

Visual enhancements and native search in UI-Kit 14

In addition to general bug fixes, UI-Kit 14 provides new font icons and enhancements to support Pega Infinity Mobile Client™ apps, such as a default native search configuration for finding case data. The improvements reflect the latest design trends and Pega Platform™ UI capabilities. By using UI Kit's sample end-user UI styling and components, you provide a consistent user experience across your applications.

In addition, the UI-Kit 14 introduces the following changes:

• The red triangle icon has been removed from error messages.
• The color of the calendar icon is now consistent with other icons.
• All caret down icons for auto-complete and multi-select lists use the caret-down.svg file.
• Checkbox alignment has been improved with the reduction of the left margin by 1px.
• The border-radius value has been reduced to 4px.
• The background and box shadow for rich text editor have been removed.
• The bottom margin for radio buttons has been removed.
• The header height of the None container format has been changed to 50px.
• The label font size has been changed to 14px.
• The label and border color have been slightly darkened.

Tertiary AJAX container support

Harnesses can now contain up to three AJAX containers which helps you to use the screen area even more efficiently and effectively organize content on the screen.

For more information, see Adding an AJAX container.

Customizable fonts for the native components of the mobile app

The mobile app executable files now include font packages, which provides more flexibility in replacing and customizing the fonts. You can now style the native header and the bottom bar more effectively, and improve readability or branding. In native elements, both text and icons support custom fonts.

For more information, see Configuring a custom font for the bottom bar.

References to parameters in text control

The enhanced Text control now supports referencing the parameters in the Property field, and a more flexible application of the Field Value, that you can now use in the Value field. As a result, you can now use more development options, increase reuse, and more accurately reference specific data.

For more information, see Adding a Text control.

Pagination for repeating dynamic layouts

Repeating dynamic layouts now support pagination, so that you can display extensive sets of data in smaller portions. Additionally, you can add custom icons or messages to inform users whether more data is available.

For more information, see "Pagination" in Configuration options for layouts.

Set a time zone for the DateTime control

The DateTime control now supports the selection of a specific time zone. Apart from the default local time zone, you can choose a Java-supported time zone or enter a property. For example, you can make it easier for a manager working in New York to schedule a task for a worker in London by configuring a calendar picker on user forms to show a date and time for Europe/London.

Beginning with this release, the calendar picker defaults to the current time in the time zone that is defined in the operator record. Previously, it defaulted to the local time zone of the system.

For more information, see Specifying a time zone for a DateTime control.

Upgrade impact

After a successful upgrade, the DateTime gadget displays the time in the current operator's locale, which is defined on the operator rule form or in the browser.  

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

If you need to display the system time from which the user has logged in, and if this is not the same as the time in the user's locale (based on the browser setting), set the Locale field in the operator ID to be blank so that the browser-based setting and the displayed time are the same as the system time.