module function · N/log
audit()
log.audit(options)
Logs an Audit message.
- Implementation
- Implemented published in npm 0.0.1
- Design
- Accepted
log.audit(message)
A
suitescript api
1log.audit({2 title: /* string, required */,3 details: /* any, optional */4});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.title | string | required | The text to appear in the Title column on the Execution Log subtab of the script deployment. Maximum length is 99 characters. If you set this value to null, an empty string (''), or omit it, the word 'Untitled' appears for the log entry. |
| options.details | any | optional | You can pass any value for this parameter. If the value is a JavaScript Object type, JSON.stringify(obj) is called on the object before displaying the value. NetSuite truncates any resulting string over 3999 characters. |
B
mynt syntax
Supported syntax · compiles today
log.audit("Reviewed")
1log.audit({2 title: "execute",3 details: "Reviewed"4});
The title is the entry point's name, so the execution log shows where a line came from. Published on npm since 0.0.1. Verified with mynt build on 13 Oct 2026.
C
community proposals
Competing syntax for audit, from GitHub Discussions. Select two or more to compare them side by side, with the syntax Mynt supports today as a baseline.
Mynt today
log.audit("Reviewed")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?