module function · N/certificateControl
createCertificate()
certificateControl.createCertificate(options)
Creates a certificate record using a file from the File Cabinet.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1certificateControl.createCertificate({2 file: /* file, required */,3 password: /* string, optional */,4 scriptId: /* string, optional */,5 description: /* string, optional */,6 subsidiaries: /* number[] or string[], optional */,7 restrictions: /* number[] or string[], optional */,8 notifications: /* number[] or string[], optional */,9 name: /* string, required */10});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.file | file | required | A File Object Members object. The file must already be uploaded to the File Cabinet. |
| options.password | string | optional | If applicable, the password associated with your digital certificate. The script ID of an API secret can be accepted. For more information, see Secrets Management . |
| options.scriptId | string | optional | The desired script ID of the certificate record. The script ID is automatically prefixed with custcertificate . |
| options.description | string | optional | The description of the certificate record. |
| options.subsidiaries | number[] or string[] | optional | The internal ID of subsidiaries associated with the certificate in either number or string format. |
| options.restrictions | number[] or string[] | optional | The internal ID of employees selected in the Restricted to Employees field for a certificate. You can enter the internal ID in either number or string format. |
| options.notifications | number[] or string[] | optional | The internal ID of employees selected in the Copy Employees field on the certificate record. You can enter the internal ID in either number or string format. |
| options.name | string | required | The name of the certificate record. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to certificateControl.createCertificate(options) today. How should it read?
C
community proposals
Competing syntax for createCertificate, 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?