Published Release Notes

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.

Building a Pega Mobile Client with custom modules

When you build a Pega Mobile Client mobile app using the Pega 7 Platform, you can now include Android or iOS custom modules. The custom modules must be included in the assets.zip file that contains the Pega Mobile Client branding and customization details.

For more information, see Building a mobile web app into a hybrid mobile app.

Remote device log retrieval from online-only mobile apps

In addition to device logs from offline-enabled mobile apps, Pega Mobile Client™ can now upload device logs from online-only mobile apps. The upload to Pega Platform™ starts when a user restarts the mobile app. You retrieve device logs from a specific device to support remote users and troubleshoot mobile apps.

For more information, see Retrieving device logs.

Improved mobile user experience with spaces

Spaces in mobile apps have been enhanced to provide a wider screen area for navigation between content tabs such as Pulse, Boards, Subspaces, and Tasks. Mobile users can now use native selection controls to choose from the same space-specific actions that are available to users of desktop-based applications. The enhancement improves the usability of spaces and promotes collaboration between mobile users.

Spaces on mobile apps do not require any additional configuration.

For more information about spaces, see Collaborating with users by using spaces.

Increased display area in mobile apps

Mobile apps now support hiding the top and bottom bars when the user scrolls down. When the user scrolls up, the bars appear again. This enhancement improves the mobile user experience by presenting more data on the screen, for example, a longer list of items.

For more information, see Advanced layout options.

Mobile apps display skeletons for the initial screen load

Android and iOS mobile apps now display a skeleton before the initial screen loads, which enhances user experience and provides faster response to user actions on complex mobile screens or over slow networks. Until the initial screen is ready to be displayed, Pega Platform™ displays an empty placeholder that imitates the actual user interface.

Skeletons for the initial screen in mobile apps do not require any additional configuration.