Published Release Notes

DateTime control enhancements

The DateTime (calendar) control has been updated. You can now show week numbers on the calendar, disable weekends so that users cannot select them as working days, show minutes in intervals, and use spinners to facilitate navigating between months and years. These design-time options make it easier for users to select valid dates and times in your applications.

For more information, see Adding and configuring a DateTime control.

Attach Content control enhancements

You can now use the Attach Content control in Pega^® Platform to configure compression options that limit the size of files created on a mobile device. For example, you can choose from predefined settings to limit video duration or image size. These settings apply when the user records a new video or takes a new photo, but they do not apply to prerecorded media.

Also, when attaching content to a custom mobile app, users can now select any type of file from any source that is available in the device's native file picker component.

For more information, see Configuring file size options for the Attach content control.

Multi-Select list control

You can add a Multi-Select list control to a user form so that application users can select more than one value for a single field. These lists save time and ensure accuracy by supplying a list of valid values for an input field. You can source a Multi-Select list control from a data page, clipboard page, or report definition.

For more information, see Adding and configuring a Multi-Select list control.

Accessibility support using WAI-ARIA roles

The Pega 7 Platform supports accessibility by using Web Accessibility Initiative Accessible Rich Internet Application (WAI-ARIA) roles. WAI-ARIA roles are a World Wide Web Consortium (W3C) ontology that specifies roles, states, or properties for each user interface element. Roles provide semantic information about features, structures, and behaviors that assistive technologies use to convey information to users.

• The dynamic container is marked as the main content area by default. When a user tabs through a page, the user can choose to follow a skip to the main content link by pressing the Enter key.
• WAI-ARIA roles are included by default on screen layouts, and each panel of the screen layout is assigned a role that is based on its position.
• Dynamic layouts can be configured with a specific WAI-ARIA role, depending on the function of the layout in the user interface.

Changes to User Interface menu in Designer Studio

The User Interface menu in Designer Studio has changed. For example, menu options related to localization are now grouped under Application readiness.

For more information, see Designer Studio - Landing Pages.

Updates to the Event Strategy rule

When you design event strategies, you can use the Filter shape for basic arithmetic and text expressions. You can also specify start conditions for the tumbling and sliding windows.

Legacy landing pages removed

The following legacy landing pages and their links in the Designer Studio menu have been removed:

• Designer Studio > Data Model > Clipboard Pages > Data Pages
• Designer Studio > Data Model > Clipboard Pages > Undefined Pages
• Designer Studio > Data Model > Classes & Properties > Class Relationships

The streamlined Designer Studio menu facilitates locating and navigating to landing pages.

For information about the replacements for these landing pages, see Deprecated features.

Integrated Application Security Checklist helps you deploy a secure application

Pega^® Platform now provides an Application Security Checklist that you can refer to when you prepare your application for deployment. By completing the recommended tasks in this checklist, you can track your progress, access instructional information for tasks, and verify that your configurations are secure.

For more information, see Preparing your application for secure deployment, Compliance Score tab, Designer Studio — Home page.

Support for custom pre- and post-JavaScript processing for offline flow actions

Developers of an offline-enabled mobile app can execute basic business logic before and after a flow action is rendered by adding their own JavaScript code into a custom user scripts bundle. Its functions must be called within a try/catch clause. The JavaScript code, to be executed before a flow action is rendered, is always called afterClientCache is called and before DisplayHarness is called.

Monitor application health on the Application Quality landing page

On the Application Quality landing page, you can view various quality-related data in one place so that you can monitor the quality of your application and correct any issues. The Application Quality landing page contains a summary of guardrails compliance, PegaUnit test coverage, and results of PegaUnit tests.

For more information, see Application Quality landing page.