SuiteScript

Changes to External Suitelet URLs

Suitelets that are available without login have updated External URLs as of May 9, 2024. The new URL is displayed in the External URL field on the script deployment record and uses the &ns-at= parameter followed by a new value. To prevent broken links to Suitelets that are accessed with hard-coded URLs, you must update those links to the new format.

Give special consideration to the following:

• All hard-coded URLs are impacted.

• Cases where the URL is resolved automatically, using url.resolveScript(options) and similar methods, do not require any action.

Hard-coded URLs can be found in various places:

• In scripts and HTML files in your account

• Occasionally in other places like script parameters

• In external systems that retrieve information or trigger actions

• Links on your Web site

• In rare cases, where a Suitelet is used as a public Web site, it might be referenced by search engines

Tips for locating and updating hard-coded URL that call external Suitelets:

• The previous format that will now result in broken links uses the &h= parameter and a different value. For example, /app/site/hosting/scriptlet.nl?script=123&deploy=123&h=ABCDFEFGHIJKLMNOPRSTUV would now be updated to /app/site/hosting/scriptlet.nl?script=123&deploy=123&ns-at=KLMNOPRSTUVABCDFEFGHIJ.

• New External URLs can be found on the Script Deployment record of Suitelets that have the Available Without Login preference enabled. Script Deployments are found in most accounts at Customization > Scripting > Script Deployments.

• See Search for Scripts Containing Hard-coded URLs with &h Parameter, SuiteAnswers article 1016553, for a possible solution to find affected URLs in your account. As with all script samples, this solution is not guaranteed to work in your account due to varying features, permissions, and settings.

For more information, see the following topics:

• Setting Available Without Login

• https.requestSuitelet(options)

• https.requestSuitelet.promise(options)

• url.resolveScript(options)

New N/pgp Module

A new N/pgp module is now available. The N/pgp module loads generated PGP keys from a secret to securely send messages to one or multiple recipients. To send an encrypted message, you must first create the contents of the message with the pgp.createMessageData(options) method. Next, use the MessageData.encrypt(options) method to securely encrypt and optionally sign the message contents. Message recipients can optionally enable configuration preferences to customize how messages are decrypted.

You can also use this module to create certificate.Signer objects to sign plain strings. For more information, see N/pgp Module.

Changes to RESTlet script and New N/scriptTypes/restlet Module

Currently, any RESTlet script that returns HTML content is determined by the Content-Type header in the HTTP request. If the Content-Type header of the HTTP request has a value, the value gets passed to the HTTP response. If there is no Content-Type header defined in the HTTP request, the default value of the HTTP response Content-Type header is HTML (or text/html).

As of September 30, 2024, any RESTlet script that does not have a defined HTTP request Content-Type header will have a default HTTP response Content-Type header of plain text (or text/plain). If you require any RESTlet scripts to have a return value in HTML format, you must update these scripts. Use the restlet.createResponse(options) method of the new N/scriptTypes/restlet module to set the RESTlet's HTTP response Content-Type header to text/html explicitly.

The restlet.createResponse(options) method lets you specify the Content-Type header for your Restlet response to ensure that it is in the format that you intend it to be. You can use this method in the return statement of your RESTlet script’s entry point functions. For more information, see N/scriptTypes/restlet Module.

Changes to the Hide in SuiteBundle Preference

Some SuiteApps and SuiteBundles may include scripts or files that were marked as Hide in SuiteBundle but must be accessed in the browser, such as client scripts or library files and assets needed on the client side. Enablement of the Hide in SuiteBundle preference for this type of file is not a valid configuration.

In preparation for this change, accounts with such SuiteApps and bundles installed have been updated to clear the Hide in SuiteBundle preference for scripts and files that have been run on the client side.

As of NetSuite 2024.2, any scripts that have the Hide in SuiteBundle preference enabled will fail to run if accessed on the client side.

Newly Supported Record Actions in 2024.2

The following table lists the newly supported record actions for SuiteScript in 2024.2.

Newly Supported Record Types in 2024.2

The following table lists the newly supported records in SuiteScript for 2024.2.

Removal of the Ext JS Library in 2025.1

NetSuite has started the process to remove the unsupported Ext JS library. If your customizations rely on this library's API, despite its lack of support, you should prepare for this removal as soon as possible.

To help you identify usages of the library in your account, a banner message will be displayed on pages that load a script using the unsupported Ext JS library. This banner display will be available in accounts running NetSuite 2024.2.

The Ext JS library will be removed in NetSuite 2025.1. The removal of the Ext JS library may break external references to it. If you want to continue using the Ext JS library, you must replace it with your own external instance of the library. Otherwise, you need to adjust your code to work without the use of the Ext JS library.

2024.2 SuiteScript Records Browser

The 2024.2 SuiteScript Records Browser is not yet available.