File Types for SSP Applications in SuiteScript Customization
Understand file types used in SSP applications for SuiteScript, including .ssp and .ss for effective web customization.
TL;DR
This article discusses the specific file types used in SuiteScript Server Page (SSP) applications, which are essential for creating and customizing web store functionalities. Understanding these file types ensures that developers can effectively implement dynamic content and request handling in their SuiteScript applications.
What Are the File Types for SSP Applications?
In SuiteScript customization, particularly when developing SSP applications, understanding the various file types is crucial. The supported file types for these applications include:
-
.ssp files: These are SuiteScript Server Pages that can be crafted using HTML and/or server-side SuiteScript. They function similarly to JavaServer Pages (.jsp) and allow the inclusion of code libraries. Developers can also utilize suitelets and RESTlets within .ssp files to enhance their web pages using JQuery.
-
.ss files: These represent special SuiteScript components known as request handlers. They can be either frontend non-HTML pages (like AJAX handlers) or backend pages that handle HTTP requests. These files are capable of generating outputs in formats such as HTML, XML, JSON, or JavaScript and can also issue redirects.
Both file types are processed on the server side, granting access to all SuiteScript APIs that are applicable in such a context. Additionally, SSP application files developed in SuiteScript 1.0 can utilize the Commerce API, facilitating web store customization.
Importance of File Types
Understanding the distinction between .ssp and .ss files not only aids in structuring your web applications effectively but also plays a significant role in ensuring compatibility with NetSuite's functionalities and APIs. This knowledge is imperative for developers seeking to maximize the capabilities of SuiteScript in web store development.
Best Practices
- Utilize .ssp for UI Rendering: When displaying dynamic content for web users, prefer using .ssp files for their support of both HTML and server-side SuiteScript.
- Employ .ss for Request Handling: Leverage .ss files for handling various HTTP requests, ensuring proper responses in the appropriate format.
- Test Thoroughly: Always test both file types in a development environment before deploying to ensure they interact seamlessly with your web store.
Additional Resources
For further guidance on implementing these file types, refer to the Sample SSP Application Code (SuiteScript 1.0) and Sample SSP Application Code (SuiteScript 2.0).
Key Takeaways
- Both .ssp and .ss files are vital for developing SSP applications.
- .ssp files are best for rendering frontend dynamic content, while .ss files handle request processing efficiently.
- Familiarity with these file types enhances capability in SuiteScript customization.
Source: This article is based on Oracle's official NetSuite documentation.
Frequently Asked Questions (4)
Are .ssp and .ss files available in both SuiteScript 1.0 and 2.0?
What types of outputs can .ss files generate for handling HTTP requests?
Do .ssp files in SuiteScript support the use of external JavaScript libraries like JQuery?
Can SSP application files access all SuiteScript APIs during server-side processing?
Was this article helpful?
More in SuiteScript
- Scheduling Map/Reduce Script Submissions in NetSuite
Learn how to schedule map/reduce scripts for one-time or recurring submissions in NetSuite, enhancing automation and efficiency.
- API Governance Units Calculation in NetSuite 2026.1
NetSuite 2026.1 introduces examples illustrating API governance unit calculations for both user event and scheduled scripts.
- Binary File Support in N/https Module for SuiteScript
SuiteScript enhances capabilities with binary file support in the N/https module, allowing improved data handling in external communications.
- Attach and Detach Operations in NetSuite 2026.1
Attach and detach operations for record relationships in NetSuite enhance data management and connectivity.
