The Workflow designer has a choice when a Workflow should initiate, an Action should be performed, or when a workflow instance in a record should Transition to another state.
Among these choices are Server Triggers which are a part of the SuiteFlow Trigger Execution Model. This trigger type is processed on the NetSuite Cloud Server Application side and classified as either Record-based, Workflow State-based, or Time-based.
Here are the references to each server trigger based on their classification:
Record-based:
Workflow State-based:
Time-based:
ℹ️ Some points to consider when working with Server Triggers:
- Workflow Custom Fields and Workflow State Custom Fields that are set under a particular record-based server trigger must be accessed on that same trigger, or else a loss of value will occur. For instance, a workflow field set on the Before Record Load trigger must be accessed on Before Record Load as well to get the value that was set on that field. Accessing the workflow field on a different server trigger will return a null value.
- Custom Formulas used on applicable workflow actions and workflow conditions use the Oracle SQL syntax. JavaScript and SuiteScript syntax will not work.
- The Execute as Admin option and Sublist Action Groups are only supported by triggers under this type.
- If a user reloads the recordwhen a record is in a state, NetSuite executes the server triggers again, starting with the Before Record Load trigger. Actions set to execute on Entry do not execute again.
- Workflow Execution Logs generated when Enable Logging is turned on in the Workflow only contain information related to this trigger type.
Let us know what you think about this topic by leaving a comment or using the reaction buttons below.
-Jack