Working with States
A workflow can have as many states as your business process needs. Every NetSuite workflow must have at least one state. Workflows without any states can't be initiated to run for a record, even if the workflow is set to Running. A workflow can have only one start state, called the entry state. It can have multiple end states, called exit states. A workflow with only one state is also known as a single state workflow.
For an overview of states and state functionality in SuiteFlow, see Workflow States and SuiteFlow Trigger Execution Model.
After you create a workflow, the Workflow Manager creates a default state called State 1. You can edit this state to change its properties and add actions, transitions, and state fields. You can also add more states or delete existing ones. A workflow must have at least two states before you can create transitions. You can create all the states required by the business process first, and then edit them and create transitions between the states.
As you set up the workflow and add states, you can use the diagrammer to drag and drop states to show the flow of the business process.
The following table describes where you can get more information about working with states:
Task |
For more information |
---|---|
Creating a state in a workflow |
|
Editing existing state |
|
Deleting a state and the effects on subsequent workflow instances |
|
Creating a state field |
|
Working with exit states |
|
Creating a non-exiting state |