SnapApp Views - Custom Buttons
on 02-03-2026 12:00 AM by SnapApp by BlueVector AI
59
Custom Buttons Guide
Custom Buttons are the primary way to add interactive logic to your application interface. While standard buttons handle basic data entry, Custom Buttons allow you to trigger specific background processes, navigate to custom URLs, or execute automated workflows directly from your Views.
Table of Contents
How to Access
Custom Buttons are managed within the individual configuration of a View. To add or edit a button:
- Navigate to Settings > UX > Views.
- Locate your desired View in the list and click the Configure (wrench) icon.
- Scroll down to the UI Customization section.
- Locate the Custom Buttons table and click + Add New.
Button Configuration
When the Add New Custom Button modal opens, you can define how the button looks and what it triggers:
| Property | Description |
|---|---|
| Name | The label displayed on the button (e.g., “Submit” or “Approve”). |
| Icon | A visual cue displayed alongside the name to help users identify the action. |
| URL Type | Defines the action logic. Options include Workflow, Action, Quick Action, or Custom for a custom URL. |
| Workflow | Select the specific automated process this button should trigger. |
| Parameter | Defines the data passed to the action (usually set to id for the current record). |
| Sequence | The numerical order determining where this button sits among other custom buttons. |
| Target | Where the action opens: New Tab, Same Tab, or in the Background. |
| Type | Defines the button’s scope: Record (appears on specific entries) or Header (top of the View). |
| Shortcut | Allows for assigning a keyboard shortcut to trigger the button action. |
| Active | A checkbox to enable or disable the button without deleting the configuration. |
Conditional Visibility (Show IF)
The Show IF field allows you to control exactly when a button appears based on specific record data. This ensures users only see actions that are relevant to the record’s current state.
- Logic: Use the Expression Builder to write a formula. If the formula evaluates to True, the button is visible.
- Example: To show an “Approve” button only when a record is in specific states like “Submitted” or “Documents Required”:
=IF([[status]]=="Submitted") OR IF([[status]]=="Documents Required")
- Example: To show an “Approve” button only when a record is in specific states like “Submitted” or “Documents Required”:
Pro-Tip: Permission Overrides Field-level permissions explicitly override object-level settings. If a button is programmed to update a field that the user’s role is restricted from editing, the action will fail even if the button is visible.
Best Practices
- Keep it Simple: Don’t clutter a View with ten buttons. If a process has many steps, consider using a Wizard or a dropdown menu for secondary actions.
- Naming: Keep labels short. “Email Client” is better than “Send an Email to the Associated Client Record.”
Thank you for following these steps to configure your SnapApp components. Building a well-structured data environment is the first step toward creating a powerful, automated application that scales with your needs.
For further assistance, email us at snapapp@bluevector.ai.
