Setting Up Autoclick for Buttons
On a mobile page of a process, you can skip the manual tapping of a button by setting up its autoclick condition. This setting automatically triggers an Action Button’s On Click Action right after a page load within a standard or custom mobile process.
To set up, in the Autoclick Condition field, you can enter a true or false value. You can also assign a condition or expression to control the action dynamically. To configure or customize this field, see Configuring Mobile Page Elements or Customizing Mobile Page Elements, respectively.
For example, you can skip the confirmation pages of standard mobile processes by adding autoclick conditions to the appropriate navigation button.
You should not set up multiple conditions that may conflict or complicate mobile process flows. On a mobile page, the app executes the autoclick condition of one button only. If you want to add autoclick conditions to multiple buttons, see how the following Action Button settings affect the evaluation sequence:
-
Disable Field Condition and Visibility Condition – The app evaluates only visible and enabled buttons.
-
Content Area and Is Primary – Buttons in the footer of a mobile page are evaluated first before those in the body. Primary buttons on the footer or body are evaluated first before any nonprimary button.
For standard mobile processes, you can configure the Autoclick Condition of standard buttons that already appear in the footer or body. Like custom buttons, standard primary buttons on the app have a blue background.
-
Display Order – Multiple primary or nonprimary buttons are evaluated based on their Display Order value.
Settings for the mobile page or other page elements may be affected by autoclick conditions, as described in the following:
-
If the mobile page has an On Load Action or After Load Action, the app completes either or both these actions first before it triggers the autoclick condition. For more information about actions, see Customizing Mobile Actions.
-
Text Box elements have an autosubmit setting for default values, which could be ignored if you also add autoclick conditions to buttons. If you set up both on the same mobile page, the app evaluates autoclick conditions before autosubmit settings. If an autoclick condition evaluates to true, any autosubmit setting might no longer be evaluated. For more information about primary buttons and autosubmission, see Assigning Default Values to Field Elements.