module function · N/ui/serverWidget

createAssistant()

serverWidget.createAssistant(options)

Creates and returns a new assistant object.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
serverWidget.createAssistant(options)
Returns
serverWidget.Assistant
Governance
None
Script types
Suitelets
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1serverWidget.createAssistant({2    title:      /* string, required */,3    hideNavBar: /* Boolean, optional */4});
Oracle reference for this method
ParameterTypeRequiredDescription
options.titlestringrequiredThe title of the assistant. This title appears at the top of all assistant pages.
options.hideNavBarBooleanoptionalIndicates whether to hide the navigation bar menu. By default, set to false . The header appears in the top-right corner on the assistant. If set to true , the header on the assistant is hidden from view.
B

No Mynt syntax yet.

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

C

Competing syntax for createAssistant, 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/ui/serverWidget · serverWidget.createAssistant(options)

Suggest syntax for createAssistant