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

Anypicker control is now available

The new Anypicker control displays a drop-down list of values that you can group into expandable categories for faster browsing. To save time and improve search accuracy, the Anypicker control filters the available values based on the characters that the user enters.

For more information, see Adding an Anypicker control.

Referencing Rule tool in Dev Studio

The Referencing Rule tool now runs in Dev Studio without the need for Adobe Flash Player. This enhancement integrates the Referencing Rule tool into your work environment, which improves productivity by reducing context switching.

For more information, see Finding rules by dependency.

PDF/UA support

PDF documents that you generate in Pega Platform™ are now in PDF/UA format. This enhancement improves accessibility for users who rely on assistive technology, such as screen readers.

For more information, see Setting PDF file versions.

Upgrade impact

With an upgrade to Pega Platform 8.4 and later, the underlying PD4ML library in Pega Platform changes from v3.10 to v4.x. Following an upgrade, most standard HTML-CSS conversions to PDF work seamlessly; however, if you use the following custom coding in their application to convert HTML to PDF, you may find that PDF generation works differently than expected or no longer works:

• Application layer Java in activities that directly link to the underlying PD4ML library
• A Rule Utility Function
• PD4ML tags in HTML fragments

For example, the following PD4ML proprietary CSS keywords are no longer supported in v4.x:

• pd4ml-page-break-border-top
• pd4ml-page-break-border-bottom

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

After you upgrade to Pega Platform 8.4 and later and find your PDF generation works differently than expected or no longer works, you should consult the latest documentation available at pd[4]ml support site. You may also consider using the Compact CSS instead of the application skin for PDF generation; for details, see Creating PDF files by using a compact style sheet.

Custom activities protection