SuiteScript 2.0 SSP Application Deployment on System Domains

SuiteScript 2.0 SSP applications must be explicitly made available on specific websites and domains. Unlike their SuiteScript 1.0 counterparts, these applications are not accessible by default, ensuring tighter control over the deployment process. This article outlines how to make these applications available on system domains.

How to Make an SSP Application Available on Your System Domain

To allow an SSP application to be accessible on your system domain, follow these steps:

1. Navigate to Commerce > Hosting > SSP Applications.
2. Click Edit next to the desired SSP application.
3. Check the box for Available on System Domain. System domains will typically use the format system.netsuite.com.
4. Click Save to apply the changes.

What Are System Domains?

System domains refer to the specific URLs that host your NetSuite applications, providing access to the functionalities you’ve implemented.

Implications of Availability

Making an SSP application available on a system domain is crucial for ensuring proper functionality and access for users. If this step is skipped, users will not be able to access the deployment via the intended domain, potentially leading to confusion and loss of service.

Related Topics

Further reading on operating SSP applications successfully can enhance your understanding:

• Create a SuiteScript 2.0 SSP Application Record
• Upload SSP Application Files to the File Cabinet
• Set Execute as Role Permissions for .ss and .ssp Files
• Sample SSP Application Code (SuiteScript 2.0)
• Debug a SuiteScript 2.0 SSP Application

With these guidelines, you can effectively manage the deployment of your SuiteScript 2.0 SSP applications on system domains, ensuring they function as intended across your NetSuite environments.

Key Takeaways

• SSP applications need explicit permissions to be available on system domains.
• Follow a simple four-step process to enable availability.
• System domains format typically uses system.netsuite.com.