Custom Button

The Custom Button trigger is a unique type of trigger that allows users to define a custom button to execute a specific action. Unlike automated triggers, this one requires manual user interaction to activate the workflow.

Configuration Options

Select Table

• Choose the table where the custom button will be available.

Custom Button Label

• Provide a name for the button. This label will appear on the button unless you opt for an icon-only visualization.

Button Position

• Decide where the button will be displayed:
  • Menu: Adds the button to the main menu of the table.
  • Popup: Places the button in the popup menu of the table.

Button Visualization

• Choose how the button will appear:
  • Full Button: Displays both an icon and the button label.
  • Just the Icon: Displays only the button icon without text.

Button Style

• Customize the appearance of the button:
  • Background Color: Select a color for the button’s background.
  • Icon: Choose an icon to represent the button visually.

Button Order

• Set the button’s order (numeric value) to control its position among other buttons.

Run on Server

Use this switch to choose where the workflow script will run.

On

The script runs on the server.

Use this option for background or non-interactive processes, for example:

- creating or updating records
- processing data
- sending emails
- calling APIs
- scheduled or automatic actions
 

Server-side scripts should not be used for actions that require direct user interaction in the browser.

Off

The script runs on the client side, in the user's browser.

Use this option when the workflow needs to interact with the user interface, for example:

- showing alerts or warning messages
- showing confirmation dialogs
- displaying HTML messages
- working with values currently visible in the form
- reacting to user actions before continuing
 

Important

If the script displays a message to the user, opens a confirmation dialog, or uses HTML content for user interaction, set Run on Server = Off.

Use Run on Server = On only when the script can run without user interaction.

Disable When No Row Selected

• You can disable the button when no row is selected. This ensures that users cannot trigger workflows that require a specific record context.

Use Case Examples

• Add a "Mark as Complete" button to tasks in a project management table.
• Provide a "Generate Invoice" button for specific records in a billing table.
• Create a "Send Notification" button to trigger a custom alert for selected users.

This trigger empowers users with direct control over workflow actions through customizable buttons, enabling tailored interaction and flexibility.