jfb-action-messages

To customize JetFormBuilder action messages per-instance, you use Mechanism B which leverages action_attributes for per-action settings, allowing you to define distinct success or error messaging directly within individual form actions.

Form-level messages use registered keys for stable, form-wide messaging via Mechanism A, whereas per-action messages utilize action-local settings through Mechanism B to customize messaging for individual action instances.

You register custom JetFormBuilder message types using the jet-form-builder/form-messages/register hook, which allows you to define stable keys for displaying consistent dynamic success or error messages across your forms.

Yes, you can display dynamic success messages by leveraging the after-send hook in JetFormBuilder, enabling contextual messaging based on the specific results of the form action execution.

You throw an Action_Exception in JetFormBuilder by passing either a registered message key or a custom message string, which then surfaces the appropriate user-facing error message during form processing.

Yes, extending Base_Action_Messages is required to modify JetFormBuilder form messages, as it provides the foundational structure for registering and surfacing custom user-facing messages within your plugin bootstrap.