Default SSP File Selection in SuiteScript Applications

Starting in SuiteScript 2.0 applications, the process of applying customizations has evolved significantly. Unlike prior versions, where logic was specified in multiple places, the default SSP file in SuiteScript 2.0 centralizes this control. This allows web store entry point customizations to be managed more efficiently, reducing configuration complexity.

What Does the Default SSP File Do?

In SuiteScript 1.0, web store customizations required identifying supported touch points both in the SSP application record and separately in domain and website setup records. SuiteScript 2.0 simplifies this process by consolidating this logic within a single default SSP file. This file acts as a centralized touch point for the domain or website, eliminating the need for repetitive setup and potential conflict.

Limitations

As of the last major update, there are currently no NetSuite SSP applications that utilize a default SSP file out of the box. However, developers have the option to create and implement their own SSP files tailored to their store's needs. It's important to note that while SuiteScript 2.0 applications can perform essential tasks like logging in the background, a default SSP file is not required for these background processes.

Selecting the Default SSP File

To choose the default SSP file for your SSP application, follow these steps:

1. Navigate to Commerce > Hosting > SSP Applications.
2. Click Edit next to the desired SSP application.
3. In the Default SSP File field, type the initial letters of the intended default SSP file and press the Tab key to locate it.
4. Finally, save the SSP application record.

Important Considerations

• As of now, there is no built-in functionality to automatically select a default SSP file based on user visits to a website or domain—this may be enabled in future releases.
• For any active SuiteScript 2.0 SSP applications on a commerce site, ensure that you directly link to the URL root of the deployed application.