Form object method · N/ui/serverWidget
addPageInitMessage()
Form.addPageInitMessage(options)
Shows a message on a form in view mode.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1objForm.addPageInitMessage({2 message: /* message.Message, required */,3 type: /* message.Type, required */,4 title: /* string, optional */,5 message: /* string, optional */,6 duration: /* int, optional */7});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.message | message.Message | required | Encapsulates the message to be shown on the form. |
| options.type | message.Type | required | The message type. |
| options.title | string | optional | The message title. This value defaults to an empty string. |
| options.message | string | optional | The content of the message. This value defaults to an empty string. |
| options.duration | int | optional | The amount of time, in milliseconds, to show the message. The default is 0, which shows the message until Message.hide() is called. If you specify a duration for message.create() and message.show(), the value from the message.show() method call takes precedence. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to Form.addPageInitMessage(options) today. How should it read?
C
community proposals
Competing syntax for addPageInitMessage, 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?