SSP Application Precedence in SuiteScript Customizations

TL;DR Opening

Understanding the precedence of SuiteScript Server Pages (SSP) applications is crucial for effectively managing customizations within NetSuite. This knowledge allows developers to control how requests are handled when multiple applications vie for the same URL and hosting root.

What is SSP Application Precedence?

SSP applications can be complex, especially when they share both a URL root and a hosting location. In such scenarios, NetSuite employs a system of precedence to determine which SSP application will respond to a given request. It’s important to note, however, that this precedence does not impact SSP applications built in SuiteScript 2.0; applications written in this version cannot share a URL and hosting root because they must each be deployed to distinct domains or websites.

How Does SSP Application Precedence Work?

• Multiple Applications: If two or more SSP applications share the same URL and hosting root, NetSuite must decide which one takes priority when a request is made. This helps to prevent conflicts and ensures that the correct application is engaged based on the desired context or conditions.
• SuiteScript 2.0 Exclusion: For SSP applications created in SuiteScript 2.0, the precedence rules are simplified, as each application must have a unique deployment scenario. That means even if the URLs are the same, these applications operate independently.

Considerations for Developers

• Ensure Unique URL Roots: When developing with SuiteScript 2.0, always deploy your applications with distinct URL roots to avoid potential deployment conflicts.
• Manage Precedence for SuiteScript 1.0: If you are using SuiteScript 1.0, familiarize yourself with the precedence configuration since multiple applications may interact through the same domain.
• Check Deployment Status: Always check which applications are actively deployed to the desired domain/website to ensure that the correct precedence is in effect.

Key Properties of SSP Applications

Developers should also be aware of the key properties associated with SSP applications, including:

• Application Folder: The specific folder in the file cabinet where customization files are stored.
• URL Root: The base URL used for accessing the assets of the SSP application.
• Supported Touch Points: Entry points in the web store from which dynamic content can be generated (specific to SuiteScript 1.0).
• Default SSP File: The file that dictates the dynamic content output of the application.
• Deployment Sites: The specific sites or domains where the SSP application is made available.

Who This Affects

• Developers: Those coding and deploying SSP applications will need to understand application precedence to avoid conflicts.
• Administrators: Admins need to manage deployment and permissions regarding SSP applications to ensure clarity in operations.
• Webstore Managers: Anyone overseeing web store functionalities will benefit from knowing how SSP applications interact under defined rules of precedence.

Key Takeaways

• SSP application precedence influences which application handles requests sharing the same URL root.
• SuiteScript 2.0 applications do not follow precedence rules due to their unique deployment requirements.
• Understanding the properties of SSP applications is crucial for successful management and utilization.