Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Mobile UI actions

Log in to subscribe to topics and get notified when content changes.

Mobile UI actions

UI actions function the same on the mobile interface as on desktop interface, but are configured on a different table: UI Action - Mobile [sys_ui_ng_action].

You can use the following types of UI actions in the mobile interface:
  • List buttons
  • Form buttons
  • Form more items (items that display when the user taps the More button)
Figure 1. UI action
Mobile UI actions

The lowest number in the Order column identifies the primary button at the top of the form.

Note: Mobile UI actions automatically reload the form when an action is submitted. You do not need to configure a UI action to make this happen.

Back navigation in the mobile interface

Mobile UI actions support back navigation when a UI action finishes. You can navigate back one logical navigation item in the current navigation stack.

When the navigate_back flag is set to true for a mobile UI action in the UI Action - Mobile [sys_ui_ng_action] table, you can move back to the previous screen.

Sometimes one or more discrete screens, or a nested or partial view of the screen, can represent a single navigation item. For this reason, back navigation can result in different UI behaviors depending on the current navigation content or device.

For example, the activity stream and form for a record are considered as one logical navigation item (the current record). However, some devices use multiple discrete screens for this navigation. When back navigation is triggered from a UI action on a form, multiple screens may be dismissed to return to a previous item, such as a list.

Note: Setting a redirect on the UI action through action.setRedirectURL(); takes precedence over the navigate_back flag.