Supported actions when working offline

When creating a custom mobile app with offline capability, bear in mind that they support a limited set of actions when offline.

The actions in Pega mobile apps that are supported offline are shown in the following table:

Note: See also the Modals or overlays for local actions section below.

Local actions are also supported if they were set up from a button, link, icon or a menu. When you launch a local action:

• Viewing a PDF file while offline is supported - see the How to set up viewing of PDF file while offline PDN article for more information.
• Pre-activities and post-activities are not supported.
• Data transforms are not supported.

Keep in mind the following information about menus that were configured by using the Show Menu action on controls:

• The default load behavior of the Show Menu action is At Screen Load in Pega Mobile Client.
• If the menu data is populated by the actions prior to Show Menu action, those prior actions will not be executed for the load type At Screen Load.
• Context-driven menus are not supported, for example, a menu in a repeating dynamic layout that populates its items based on the row context will not work in Pega Mobile Client.

Modals or overlays for local actions

You can launch a local action using a modal or an overlay while working offline. Nested overlay configuration is supported similar to the desktop case. A modal or overlay displays full screen in an app running on a mobile device. A local action is configurable at design time, for instance, for a button, icon or link, in any section in the new or perform harness. While offline, local action changes that are submitted are kept on the mobile device and eventually synchronized with the server when the application comes online.

Customized labels for modal or overlay buttons are supported in offline mode. The labels are configured on the Actions tab of a Flowaction rule form. Hiding the default buttons of a flow action is also supported. Template, button label and formats can be customized. For mobile apps, you can indicate at design-time, whether a modal or overlay should appear on a full screen or not.

Note: When configuring a local action for a full screen modal and you need to also customize the format applied to the button in the pyModalTemplate section that invokes the local action, make sure not to remove the existing Modal button array format which is configured on the dynamic layout containing the button. Overriding this format causes issues with the modal display.

You can also set the transitions for the modal or overlay initial display and closing. The transitions that are listed below are tied to CSS classes. You can configure their reveal or closing effect in the local action settings to one of the following:

• From top / From bottom
• Fade in
• Shrink / Grow
• From left / From right
• Vertical flip
• Reverse the reveal effect (closing effect, only) - uses the opposite of the chosen reveal effect

Note: If no transitions are configured then the default ones will be used.

Open topic with navigation