Published Release Notes

Grid cascading filtering

At run time, filtering a grid by column yields accurate results as filter criteria cascade down when filtering by column heading. The filter panel displays only those values that apply based on other filter criteria. Values are filtered on both value and range.

Internet Application Composer mashup code generation

Case types can be added to an external web page by using the mashup code created in Case Designer. The mashup code is custom HTML that can be added to Internet Application Composer (IAC) codes.

The Actions menu in Case Designer includes the ability to automatically generate IAC HTML from a case type. The HTML is then copied and pasted into the target web page through standard IAC options.

The generated code is optimized for responsive web sites and responsive Pega applications. See Generating a mashup code in case configuration.

Edit application elements at run time by using Live UI

Live UI supports the addition, deletion, or reordering of UI elements within the run-time portal. Move elements by dragging and dropping within the tree. Elements can be added, deleted, and moved within or between dynamic layouts at run time by using Live UI.

Full-screen menus improve mobile navigation

A new full-screen menu setting for enhanced mobile functionality provides a smooth and seamless mobile navigation experience. Previously, regular drop-down menus were difficult to navigate on a mobile device. Select Component styles > Menus > Menu Bar > Display "Show Menu" as full screen menu to enable and configure this setting in a Skin form.

Personalize your dashboard with widgets and templates

New personalized dashboards can be customized and shared by end users. Select a default template or create your own. Choose from one of several default widgets or design a configurable widget to provide core business metrics to your users. From the new Settings tab, you can select whether a section is a template or widget.

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”.

All search data is encrypted

All search data in Pega Cloud deployments is now encrypted, both at rest and in transit. The encryption of search data makes search compliant with regulatory requirements.

For more information about search, see Full-text search.

Authentication service for basic credentials

A new type of authentication service is available for authenticating operators by using basic credentials (user ID and password). The default Pega Platform™ login is now an instance of this type of authentication service. All basic credentials authentication services include mobile authentication with the OAuth 2.0 protocol and Proof Key for Code Exchange (PKCE). You no longer have to create a custom authentication service to support mobile applications.

For more information, see Configuring a basic authentication service.

Unauthenticated sessions transition seamlessly to authenticated

A new authentication service type allows a guest user to use an application without logging in, and to be prompted to authenticate later in the session. This enhancement supports scenarios such as online shopping portals where a user can browse for items and load a shopping cart as a guest but be prompted for credentials at checkout.

For more information, see Configuring an anonymous authentication service.

Create single sign-on authentication services from App Studio

You can create and enable single sign-on (SSO) authentication services from a new landing page in App Studio. From this new landing page you can also configure new SAML and OpenID Connect authentication services to provision users. For more information, see Creating a SAML SSO authentication service and Creating an OIDC SSO authentication service.