SearchTask object method · N/task
addInboundDependency()
SearchTask.addInboundDependency()
Adds a scheduled script task or map/reduce script task to the search task as a dependent script.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
objSearchTask.addInboundDependency(dependentScript /* task.ScheduledScriptTask | task.MapReduceScriptTask, required */);| Parameter | Type | Required | Description |
|---|---|---|---|
| dependentScript | task.ScheduledScriptTask | task.MapReduceScriptTask | required | The script to add as a dependent script to the search task. Use task.create(options) and the task.TaskType enum to create a script task with a type of SCHEDULED_SCRIPT or MAP_REDUCE . This script task is a task.ScheduledScriptTask object or a task.MapReduceScriptTask , and you can add this script task as a dependent script to the search task. The dependent script is processed when the search task is complete. You can add only one dependent script per call to SearchTask. addInboundDependency() . |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to SearchTask.addInboundDependency() today. How should it read?
C
community proposals
Competing syntax for addInboundDependency, from GitHub Discussions. Select two or more to compare them side by side.
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,saveandRef[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?