🧩 Feature: Consistent Prompt User Options Inside Trigger Automation Confirmations
📝 Description
When using Trigger automation as an On click event and enabling Ask for confirmation, the confirmation dialog only supports a single Message field.
However, when using a standalone Prompt user action, additional configuration options are available, such as:
- Title
- Message
- Button labels
- Button styles
- Other prompt‑level settings
This creates an inconsistency in how user prompts are configured and displayed. The confirmation prompt inside Trigger automation should offer the same configuration options as the standalone Prompt user action.
💡 Use Case
As a Budibase user, I want to:
- Configure confirmation prompts inside Trigger automation with the same flexibility as standalone Prompt user actions.
- Set titles, messages, and button labels consistently across all prompt dialogs.
- Maintain a unified UX for all user‑facing confirmation flows.
- Avoid workarounds or branching logic just to achieve a richer confirmation dialog.
🔍 Current Pain Points
- Trigger automation confirmations only allow a single message field.
- Standalone Prompt user actions offer more configuration options.
- Inconsistent UX across different prompt mechanisms.
- Limited control over confirmation dialogs when tied to automations.
- Requires unnecessary workarounds to achieve consistent UI behavior.
🎯 Expected Behavior
- Trigger automation → Ask for confirmation should expose the same configuration options as a standalone Prompt user action.
- All prompt dialogs should support:
- Title
- Message
- Button labels
- Button styles
- Any additional fields available in Prompt user
- Prompt behavior should be consistent regardless of where it is invoked.
🚀 Impact
- Creates a unified, predictable prompting experience.
- Improves UX consistency across apps.
- Reduces builder friction and eliminates workarounds.
- Makes Trigger automation confirmations feel like a first‑class feature.
📸 Screenshots
Current
Future
📌 Additional Notes
- This enhancement aligns with existing Prompt user capabilities.
- Ensures future improvements to Prompt user automatically apply across all prompt contexts.
🧩 Feature: Consistent Prompt User Options Inside Trigger Automation Confirmations
📝 Description
When using Trigger automation as an On click event and enabling Ask for confirmation, the confirmation dialog only supports a single Message field.
However, when using a standalone Prompt user action, additional configuration options are available, such as:
This creates an inconsistency in how user prompts are configured and displayed. The confirmation prompt inside Trigger automation should offer the same configuration options as the standalone Prompt user action.
💡 Use Case
As a Budibase user, I want to:
🔍 Current Pain Points
🎯 Expected Behavior
🚀 Impact
📸 Screenshots
Current
Future
📌 Additional Notes