Published Release Notes

Text Input control number type does not validate

When a Text Input control type is set to "Number" in the Presentation tab:

• Validation does not trigger and the field is blanked out when a user submits the form.
• If a value other than a number is entered, the browser sends an empty value, and the value is not validated.
• In the Clipboard, the field value displays as empty.
• If the field is required, the validation displays.

This issue occurs when using both the Chrome and Safari web browsers, and is a result of browser behavior for the HTML5 type=“number”. To fix this issue when using these browsers, do not use the "Number" type in Presentation tab of a Text Input control. Instead, the type should be set to "Text".

Custom DX API attributes for auto-generated controls

Auto-generated controls now include the option to add custom attributes for use with the Pega Digital Experience (DX) API. The attributes are part of the DX API response to the front end and you can use them to modify the run-time behavior of the UI elements in your application. For example, you can add an attribute to a field that displays a tooltip text for that field at run time. This enhancement introduces significant flexibility to application development and gives you greater control over UI components.

For more information, see Adding custom attributes for version 1 DX API to auto-generated controls.

Enhanced run-time behavior of the currency and number controls

The currency and number controls now display separators at run time, even as the user types the values. When the user enters more than three digits, a locale-dependent separator immediately groups the digits into thousands in real time. For example, when a user who is based in the U.S. types 100000, the input field displays the number as 100,000. The currency control additionally displays currency symbols at all times, whether the input field is in focus or not.

This enhancement improves clarity and the user experience because the user no longer needs to move away from the field to see the formatting of the input, and typing long strings of numbers is now more convenient.

For more information, see Controls.

Access REST services and APIs by using OAuth 2.0

You can now allow external client applications to access REST services on your behalf by using the OAuth 2.0 protocol client credentials grant. The Pega 7 Platform acts as an OAuth 2.0 provider to grant trusted applications access to functions in Pega 7 Platform applications. Additionally, you can provide access to the Pega API by using OAuth 2.0.

New menu design options with the auto-generated menu control

Usability and responsive capabilities have been enhanced with a new auto-generated menu control offering multiple design options and configurations. New display options include text, descriptions, badges, and responsive vertical in-line menus. Loading options include:

• At screen load
• Defer load
• On first use
• On every use

Show menu controls for existing applications can be upgraded using the Upgrade Show Menu button in the HTML5 Readiness feature.

Menu created using the auto-generated menu control

Support for controlling binary file upload in Pega Mobile Client

The Client Store API of Pega^® Mobile Client has been modified so that you can suspend and resume the process of uploading binary files to the server. You can also check the state of the file uploading process. As a result, custom mobile app users can process their work items without having to wait for the synchronization process to finish.

For more information, see Pega Mobile Client API methods for controlling binary data upload and Client Store API.

VTable dispatch mechanism for HTML control execution improves performance

Pega® Platform now uses an optimized VTable dispatch mechanism to manage rule execution for the Text Input and Formatted Text Input controls. This change improves performance by eliminating the dependency between stream rules and HTML controls during rule assembly. Disabling this feature will have a negative effect on performance and is not recommended. However, you can disable this feature by adding the following configuration parameter:

Name: assembly/section/control/vtable
Value: false

Number and text input controls on Android devices may not display the correct keyboard

When running a Pega 7 application on a device using the Android operating system, pxNumber and pxTextInput controls may not display when using the desired on-screen keyboard. This happens when the number or text input type is set to number.

At design time, the input type is selected in the Editable Format section of the Presentation tab in the Cell Properties panel for a pxNumber or pxTextInput control. Due to a known limitation in some versions of the Android OS running on some devices, the keyboard displayed at run time may not support entry of decimal values when a Number type keyboard is specified.

To resolve this issue, use the Phone type when numbers with decimal values may be required. Using the Phone type displays a numerical phone keyboard. The Android phone keyboard includes both commas and periods so that decimals may be entered.

The Phone type selected in the Presentation tab of a Number control

Note that this issue only occurs on Android devices. It is recommended that applications for iOS continue to use type=“Number”.

Experimental high-speed data page support

An experimental implementation of high-speed, read-only data pages is available. This implementation is useful when data pages are used to hold static data that is used repeatedly. You can enable this feature for a specific read-only data page from the Load Management tab of the data page rule form by clicking Enable high-performance read-only data page. This feature does not support full clipboard page functionality; use with caution.

The following functionality is supported:

• Basic page and property access (read and write properties) for all normal data types
• Hierarchical data page structure (pages within pages)
• Dictionary validation mode
• Read-only data pages

The following functionality is not supported:

• Declarative rules
• Page messages
• Complex property references
• Saving pages to a database
• API access to the data page

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.