Close popover

Table of Contents

Understanding offline-supported local actions

Version:

Offline-enabled mobile apps support local actions to a certain extent. By learning about the local actions, you can ensure that your offline-enabled mobile app that uses such actions operates reliably.

Users initiate local actions by clicking or tapping buttons, links, icons, or menus to perform optional tasks that do not move a case closer to resolution. When you design an application that users can access with an offline-enabled mobile app, you use available actions from a predefined list, and the following considerations apply.
Preactivities and postactivities are not supported except with data transforms, and when you create custom JavaScript functions that are run in offline mode.

Modal and overlay configuration for local actions

Users can start a local action by using a modal dialog box or an overlay when they work offline. On a mobile device, modal dialog boxes and overlays take the full screen. You can configure a local action in any section in the New or Perform page. When the device is offline, local action changes that users initiate are preserved on the device and synchronized with the server when the offline-enabled mobile app regains network connectivity.

Customized labels for modal dialog box buttons or overlay buttons are supported offline. You configure the labels on the Actions tab of a flow action rule form. Hiding the default buttons of a flow action is also supported. You can customize the template, button label and formats.

When you configure a local action for a modal dialog box, and you customize the format applied to the button in the pyModalTemplate section that invokes the local action, do not remove the existing Modal button array format that is configured on the dynamic layout that contains the button.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.