SuiteFlow Workflow Initiation Trigger Timing in NetSuite

For workflows that initiate on record creation or update, Trigger Type determines when SuiteFlow enters its entry state. Choose Before Record Load, Before Record Submit, After Record Submit, or - All - based on record-processing timing. The broad option can also initiate the workflow when a record is viewed.

What must be configured for workflow initiation?

When a workflow is configured to initiate on a create or update event, selecting that event is not sufficient by itself. You must also select an initiation trigger in the Trigger Type dropdown list.

The selected trigger determines the record-processing point at which the workflow initiates and the record enters the entry state. This is distinct from configuring actions and transitions within workflow states: initiation determines when the workflow starts, while state configuration determines what runs after the record enters a state.

The source documentation identifies the Trigger Type dropdown but does not specify a navigation path for reaching it.

Which Trigger Type should you select?

Why does the - All - option need special attention?

- All - is not limited to a save operation. It initiates the workflow for any triggering event. The documented example is a record view: because viewing a record executes Before Record Load, a workflow using - All - initiates during that view.

That scope is why Oracle recommends a more specific initiation trigger. A workflow that should begin only as part of submission can use a submit-based trigger instead of a setting that also responds to record loading and viewing.

When reviewing a workflow that uses - All -, account for the record interactions named in the documentation:

• Viewing a record
• Clicking New
• Clicking Edit
• Clicking Save

How do server and client triggers differ?

SuiteFlow triggers are based on events that occur while NetSuite processes a record. They can determine when a workflow initiates, when actions run, or when a record transitions to another workflow state.

SuiteFlow has server triggers and client triggers. You can start workflows only on server triggers. Client triggers can run supported actions in response to user interaction, but transitions do not execute on client triggers.

The distinction matters when planning workflow behavior around a save. The source gives the following examples:

• Use a client trigger when users should be alerted to change a field before submitting.
• Use a server trigger when users should be notified after submitting.

Server triggers occur when a record is read from or written to the NetSuite database, or when a record enters or exits a workflow state. NetSuite classifies server triggers as record-based, workflow-based, or time-based. The Trigger Type choices discussed here are tied to loading and submitting records.

Related coverage: N/workflow module members for workflow control and workflow trigger task management.

What runs after the record enters a workflow state?

After a record enters a workflow state, SuiteFlow runs actions and transitions in a documented order:

1. Entry actions execute the first time the record enters the state, followed by Entry transitions.
2. Actions configured for the trigger on which the record entered the state execute.
3. Where applicable, transitions configured for that same trigger are evaluated and executed.
4. If the record transitions to another state, Exit actions execute before it moves to the next state.

For the same server trigger, actions execute before transitions. This ordering applies to the trigger-specific processing after the record has entered the state.

The general sequence differs depending on the record action:

A form change made during Before Record Load can remain visible on the rendered form even when a transition moves the record to another state. A state transition therefore does not necessarily prevent a user-interface change made during record load from appearing.

How should timing guide the choice?

Choose the trigger that matches the point at which the workflow must initiate:

• Choose Before Record Load when initiation must occur as the record is loaded through New, Edit, or viewing the record.
• Choose Before Record Submit when initiation must occur after Save is clicked but before NetSuite writes the record data to the database.
• Choose After Record Submit when initiation must occur after NetSuite writes the record data to the database.
• Use - All - only when initiation on any triggering event is intended; Oracle recommends a more specific trigger where possible.

The choice also establishes the trigger context for the workflow's first state. If actions and transitions are configured for the trigger that brought the record into that state, the documented action-before-transition order applies. If Before Record Load actions modify the form, those changes can remain visible even if processing moves the record to another state.

Who This Affects

• Workflow administrators and owners: Must select Trigger Type when configuring workflows that initiate on create or update events.
• Workflow designers: Need to align entry actions, trigger-specific actions, and transitions with the documented execution order.
• Users who view, create, edit, or save records: May encounter workflow behavior at different points depending on the selected trigger, especially when - All - is used.
• Teams using client-triggered actions: Need to account for the fact that client triggers can run supported actions but cannot start workflows or execute transitions.

Key Takeaways

• A workflow that initiates on a create or update event also requires a Trigger Type selection.
• Before Record Load initiates on New, Edit, and record viewing.
• Before Record Submit occurs after Save is clicked and before the database write; After Record Submit occurs after the write.
• - All - initiates for any triggering event, including a record view, so Oracle recommends a more specific trigger when possible.
• Only server triggers can initiate workflows. Client triggers can run supported actions but do not execute transitions.
• Within the same server trigger, actions execute before transitions; Entry actions execute only on the first entry into a state.