SSP Application Deployment Methods...

Starting with the deployment considerations for SuiteScript Server Pages (SSP) applications, it is crucial to understand how these applications differ in capability and deployment methodology compared to other scripting options like Suitelets and RESTlets. This article outlines the differences in deployment strategies, supported services, and authentication mechanisms between Suitelets, RESTlets, and SSP applications.

What Are SSP Applications?

SSP applications, utilizing SuiteScript, are important for customizing and extending web store functionalities. Understanding their deployment characteristics helps developers and administrators make informed decisions about which scripting method to use based on their specific needs.

Deployment Comparison of Different Scripting Methods

The following table summarizes the deployment characteristics and capabilities of Suitelets, RESTlets, SSP applications, and Scriptable Carts:

Feature	Suitelet	RESTlet	SSP Application	Scriptable Cart
Deployment Model	One per script	One per script	One per folder	Many per form or Record Type
Named URLs	X	X	S	X
Touch Points to override NS pages	X	X	S	X
Touch Points to Extended Apps	S	S	X	X
Bundleable	S	S	S	S
Debugger	S	S	X	S

Understanding the Table Symbols

S (Supported): This feature is available.
X (Not Supported): This feature is unavailable.
- (Not Recommended): This feature should not be used.
O (Optional): This feature is optional based on specific use cases.

Key Considerations

When deciding on the appropriate scripting method:

Analyze the customization's deployment model and requirements.
Evaluate the ease of debugging and the bundle capabilities for reuse.
Consider how touch points interact with the overall functionality involved in deploying to forms or record types.

In conclusion, understanding these deployment differences helps determine the best approach for implementing your NetSuite solutions effectively.

Who This Affects

Developers: Understanding these options is critical for setting up effective web applications using NetSuite's capabilities.
Administrators: Responsible for ensuring that deployment methods align with organizational goals and technical requirements.

Key Takeaways

SSP applications differ in deployment structures compared to Suitelets and RESTlets.
Each method carries unique features and restrictions, influencing how they can be utilized in web customization.
A clear understanding of these different capabilities can lead to better application design and implementation strategies.

Frequently Asked Questions (4)

Can SSP applications be bundled for reuse in NetSuite?

Yes, SSP applications can be bundled for reuse, similar to Suitelets, RESTlets, and Scriptable Carts.

What deployment model do SSP applications use?

SSP applications are deployed using a 'one per folder' model, which differs from the 'one per script' model used by Suitelets and RESTlets.

Do SSP applications support Named URLs?

No, SSP applications do not support Named URLs, unlike Suitelets and RESTlets which do.

How do SSP applications interact with NetSuite pages and extended apps?

SSP applications support touch points to override NetSuite pages but do not support touch points to extended apps, which is the opposite of Suitelets and RESTlets.

SSP Application Deployment Methods and Comparison