mynt

module function · N/task

checkStatus()

task.checkStatus(options)

Returns a task status object associated with a specific task ID.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
task.checkStatus(options)
Module
N/task
Returns
task.CsvImportTaskStatus | task.DocumentCaptureTaskStatus | task.EntityDeduplicationTaskStatus | task.MapReduceScriptTaskStatus | task.QueryTaskStatus | task.RecordActionTaskStatus | task.ScheduledScriptTaskStatus | task.SearchTaskStatus | task.SuiteQLTaskStatus | task.WorkflowTriggerTaskStatus
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1task.checkStatus({2    taskId: /* string, required */3});
Oracle reference for this method
ParameterTypeRequiredDescription
options.taskIdstringrequiredUnique ID of the task to check the status of.
B mynt syntax

No Mynt syntax yet.

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

C community proposals

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

All discussions

Loading proposals from GitHub…

D suggest an alternative

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/task · task.checkStatus(options)

Suggest syntax for checkStatus