module function · N/task/accounting/recognition

checkStatus()

recognition.checkStatus(options)

Checks the status of a submitted merge task.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
recognition.checkStatus(options)
Returns
recognition.MergeArrangementsTaskStatus
Governance
50 units
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2019.2
call shapefrom Oracle's parameter table
1recognition.checkStatus({2    taskId: /* number | string, required */3});
Oracle reference for this method
ParameterTypeRequiredDescription
options.taskIdnumber | stringrequiredThe task ID of the merge task to check. The task ID is assigned to the merge task when you call recognition.create(options) .
B

No Mynt syntax yet.

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

C

Competing syntax for checkStatus, 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/task/accounting/recognition · recognition.checkStatus(options)

Suggest syntax for checkStatus