Environment: NetSuite, standard Administrator role, Sales Order (Transaction record type, Sales Order sub type).
Goal: A SuiteFlow workflow adds a manually-clicked button to the Sales Order form ("Send Confirmation") so staff can trigger an order confirmation email for orders entered directly in NetSuite (not through the web store). Not automatic — deliberately click-triggered.
The problem: The Add Button action is fully configured, the workflow demonstrably runs (record correctly enters the button's state, workflow history shows Active, logging is on), but the button itself never renders anywhere — not in the main button bar, not in the Actions dropdown/overflow menu, and not found via a browser text search (Ctrl+F) of the rendered page. This is true in every combination we've tested:
Custom transaction form and the plain Standard Sales Order form
View mode and Edit mode
Pre-existing orders and brand-new orders (ruling out a stale workflow instance)
Current configuration:
Workflow: Record Type = Transaction, Sub Type = Sales Order. Initiation: Event Based, Trigger On = Before Record Load, Event Types = On Create + On View or Update, Contexts = User Interface. Release Status = Testing, Execute As Admin = checked, Enable Logging = checked.
State: "Awaiting Confirmation" (start state) contains the Add Button action.
Add Button action: Label = "Send Confirmation", Trigger On = Before Record Load, Event Types = tried both a narrow set (Edit + View) and Select All (all 6), Contexts = tried both narrow (User Interface only) and broad (all except Web Store). Condition = Sales Order : Status = Pending Fulfillment. Save Record First = checked, Check Condition Before Execution = checked. Active = checked (green check in the action list).
Transition: Awaiting Confirmation → Confirmation Sent. Transition On = Before Record Submit, Execute On Button = correctly points at the "Send Confirmation" button action. Event Types and Contexts on the transition have also been tried both narrow (Create only) and broadened to match the action.
What we've ruled out:
Custom form restricting the button — tested Standard Sales Order form directly, same result.
Client script interfering — Custom Code tab on the custom form is empty.
Role/permissions — Administrator role, full access, has been used throughout.
Stale workflow instance — reproduced on freshly created orders, not just the original test record.
The button config not matching NetSuite's own documentation — cross-checked against the official "Add Button Action" SuiteAnswers article (Answer ID 11487); our setup matches their example (approve/reject buttons on a PO) field for field.
Narrow vs. broad Event Types/Contexts on the action and the transition — tried both, no change in either case.
A form-level "enable this button" toggle — checked both "Standard Actions" and "Custom Actions" tabs on the custom transaction form; neither lists or references workflow-driven buttons at all.
We also compared against a similar community thread ("Workflow Action 'Add Button' Not Displaying or Functioning on Transaction Record") where the reporter's button did render but didn't transition correctly due to a missing outbound transition from its state. Our situation is a level earlier than that — the button doesn't render at all, so we can't even get to testing the transition/click behavior.
Question: Has anyone run into an Add Button workflow action that simply never renders under any configuration, despite the rest of the workflow (state entry, logging, conditions) clearly executing correctly? Is there an account-level feature or setting — beyond the base Workflow/SuiteFlow feature, which is obviously already on since other workflows run daily — that specifically gates whether workflow-added buttons are rendered in the UI? Any pointers on what else to check before we open a support case would be appreciated.