Bundling SSP Applications in NetSuite SuiteBundler

The process of bundling SuiteScript Server Pages (SSP) applications allows developers to package their custom web applications for distribution to other NetSuite accounts. After creating an SSP Application record and uploading the necessary assets to the file cabinet, you can utilize the Bundle Builder feature to create a SuiteApp that can be shared.

How to Bundle SSP Applications

Once you have created your SSP Application, follow these steps to bundle it using the Bundle Builder:

1. Access the Bundle Builder: Navigate to Setup > Customization > SuiteBundler > Create Bundle if the SuiteBundler feature is enabled. Make sure an administrator has enabled the Create Bundles With SuiteBundler feature.
2. Enter Bundle Basics: In Step 1, provide basic definitions for your bundle. This includes the name, description, and any other fundamental information.
3. Set Bundle Properties: In Step 2, add optional descriptive information that assists users in understanding and finding the bundle.
4. Select Objects: In Step 3, you will find your SSP applications listed. By selecting an SSP application, both the SSP Application record and its corresponding files in the file cabinet are included in the bundle.
5. Review Preferences: In Step 4, review the selected objects and set preferences for how they will be applied upon installation. You have the option to lock certain objects to prevent unauthorized modifications in target accounts.
6. Finish and Share: Conclude the process by completing the Bundle Builder, ensuring all necessary sharing settings are applied.

Important Notes About Bundling SSP Applications

• When a bundle containing an SSP application is installed in a target account, the full application record along with all files are copied to a designated folder:

  <Default Target HTML Hosting Root>: /SSP Applications/<Application Publisher>/<Application Name>

• As of the 2019.1 release, updating an existing bundle with an SSP application does not change script deployments in the target account. To clarify, existing deployments will not be overwritten, and the Log Level and Status fields will remain unchanged. These fields can be viewed on the Script Deployment page.

Who This Affects

The bundling process impacts the following roles:

• Developers: Those creating SSP applications.
• Administrators: Individuals responsible for configuring Bundle Builder and SuiteApp permissions.

Source: This article is based on Oracle's official NetSuite documentation.

Key Takeaways

• Use Bundle Builder to package SSP applications for easy distribution.
• Secure application files by locking them during the bundling process.
• Understand the impact of update limitations on script deployments in bundles.