Published Release Notes

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

The Create Build button appears grayed out when configuring and building a mobile application

When you attempt to configure and build your Android or iOS mobile application from the Mobile tab, the Create build button might appear dimmed. This issue occurs if any of the access roles in the access group were cloned from the PegaRULES:SysAdm4 access role.

Refer to Troubleshooting Pega Mobile Client to learn how to fix this issue in your application.

Offline configuration limitation

When enabling the offline capability for a case type, do not select the Enable offline check box in Case Designer because it incorrectly sets the locking strategy. Instead, select the Enable offline mode check box on the Advanced tab of the Case Type form.

To open the Case Type form from Case Designer, click Open on the Actions menu.

Internet Application Composer (IAC) renamed to Pega Web Mashup

The name of Internet Application Composer (IAC) has changed to Pega Web Mashup.

For more information, see Pega web mashups for embedding Pega Platform UI in external web pages.

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.

Conditional online and offline map display

The way an Address Map control behaves in a offline-enabled mobile app has changed. When a mobile app is online, a live Google map is loaded as expected. If the mobile app goes offline, a predefined image of a map is loaded instead.

Troubleshooting Pega Mobile Client on the login screen

An offline mobile developer can now troubleshoot issues that are not related to incorrect credentials when signing in to the Pega Mobile Client app. On the app login screen, an alert box displays where the user can click a link to examine current log files to troubleshoot the issue. The contents of the displayed log file can be filtered.

For more information, see Troubleshooting Pega Mobile Client.

New Pega Mobile Client debugging options

The Mobile tab on the Application form contains two new options: a check box for enabling debugging in the Pega Mobile Client app, and a drop-down field for setting the log level to one of the following levels: Silent, Error, Warning, Info, or Debug.

For more information, see Mobile settings reference.

Ability to view a PDF file while offline

Users of offline-enabled mobile apps can now tap a button to view a PDF file, regardless of whether the user is online or offline. The associated button, link, or icon must have a Run Script action defined that calls the pega.ui.pdf.view() function with two parameters: applicationName and pdfName. The PDF file itself must be uploaded to a Rule-File-Binary rule.

For more information, see How to set up viewing of PDF file while offline.

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.