module function · N/workflow

initiate()

workflow.initiate(options)

Initiates a workflow on-demand.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
workflow.initiate(options)
Returns
number
Governance
20 units
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1workflow.initiate({2    recordId:   /* string | number, required */,3    recordType: /* string, required */,4    workflowId: /* string | number, required */5});
Oracle reference for this method
ParameterTypeRequiredDescription
options.recordIdstring | numberrequiredThe internal ID of the base record.
options.recordTypestringrequiredThe record type ID of the workflow base record. Use values from the record.Type enum. This is the Record Type field on the Workflow Definition Page .
options.workflowIdstring | numberrequiredThe internal ID (number) or script ID (string) for the workflow definition. This is the ID field on the Workflow Definition Page .
B

No Mynt syntax yet.

Nothing in the language compiles to workflow.initiate(options) today. How should it read?

C

Competing syntax for initiate, from GitHub Discussions. Select two or more to compare them side by side.

All discussions

Loading proposals from GitHub…

D

Write the Mynt you wish you could write.

A good proposal shows the syntax, the SuiteScript it should become, and argues for it: why it is clearer, how it fits the rest of the language, what it makes harder.

  • Clarity. Does it say what happens, without ceremony?
  • Consistency. Does it read like load, save and Ref[field]?
  • Expressiveness. Does it cover the cases people actually write?
  • Honesty. Does it hide a NetSuite cost, such as governance, that a reader should see?

N/workflow · workflow.initiate(options)

Suggest syntax for initiate