Mobile UI actions and desktop UI actions are two different entities; the key to using mobile UI actions is to first understand the differences between the two interfaces. When using UI actions, here are a couple of things to note:

• The UI actions on your mobile are not the same as what you see on your desktop.
• The UI actions you've created in the desktop UI will not be visible in the mobile UI, and vice versa.

Here's where you can find them:

• Desktop UI actions are stored on the [sys_ui_action] table and can be seen by navigating to System UI > UI Actions.
• Mobile UI actions are stored on the [sys_ui_ng_action] table and are accessible by navigating to System Mobile UI > UI Actions - Mobile.

Mobile UI Action Visibility & Locations

In the desktop UI, there's a related list on the UI action form called UI Action Visibility that's used to restrict specific views. When using Mobile UI Actions, keep in mind:

• Showing a desktop UI action on the mobile view will not give a desktop UI action visibility in the mobile UI.
• There is no equivalent related list for the Mobile UI Action form. This is because the mobile UI does not support multiple views. It will only use the Mobile view, and all mobile UI actions will automatically use this_._

As with the desktop UI, Mobile UI Actions buttons can appear in different spots when you select the check boxes on the UI Action form. These mobile locations include:

• List button: The UI Action appears on record lists for the table specified in the Table field.
• Form button: The UI Action appears on forms for records on the table specified in the Table field.
• Form more item: The UI Action appears in the More button, which appears as an ellipsis in the lower right corner of the mobile form.

Mobile UI Actions & Scripting

Again, as with desktop UI Actions, mobile UI actions can contain scripts in both the condition and script fields; however, there are some differences and limitations for client-side scripting for the mobile UI. One change in particular is the difference between Mobile and Desktop URL structure, which you'll need to know when using actions like action.setRedirect.

You can find out more about scripting and mobile UI actions here: Mobile Client GlideForm (gfrom) Scripting.

Need more help with mobile UI issues?

KB0551387 - The action.setRedirectURL method is not working for Mobile UI actions. (Fixed as of Eureka Patch 10, Fuji Patch 3.)

KB0535114 - Mobile UI Actions appear on new records when condition has current. (Fixed as of Eureka.)