In SuiteScript 1.0 SSP applications, the logic of which customizations should be applied at which web store entry point is defined by specifying supported touch points in the SSP application record and by selecting touch points in the domain and website setup records. In SuiteScript 2.0 SSP applications, the default SSP file contains this logic. Defining this in a single SSP file removes the need to specify supported touch points on the SSP application record and also removes the need to select touch points on the domain and website setup records. Instead, the default SSP file contains within itself the logic of which customizations should be used for each web store entry point and acts as a single touch point for the domain or website.
At present there are no NetSuite SSP applications that contain a default SSP file; however, you can develop and use your own.
You can also use SuiteScript 2.0 SSP applications to perform background services, such as logging. This type of background SSP application does not need a default SSP file because it is not triggered by a user visiting the website.
As of 2018.2, it is not possible to select a default SSP file for a domain or website. This ability will be available in a future release. This means that, at present, you cannot select a default SSP file to trigger automatically when a user visits the website or domain. If you want to use a SuiteScript 2.0 SSP application on a commerce website, you must provide a direct link to the URL root at which it is deployed. SSP applications that use SuiteScript 2.0 can also be used for backend processing, for example, logging.
To select the default SSP file for an SSP application:
Go to Setup > SuiteCommerce Advanced > SSP Applications.
Click Edit next to an SSP application.
In the Default SSP File field, enter the first few letters of the default SSP file for the SSP application and then press the Tab key to locate the file you need.
Save the SSP application record.