Bundle SSP Applications for SuiteApp...

TL;DR Opening

After creating an SSP Application and uploading its assets, you can bundle it using the Bundle Builder in NetSuite. This process allows you to prepare the application for distribution to multiple NetSuite accounts while controlling user permissions on the application files.

How to Bundle an SSP Application

Once your SSP Application record is established and the necessary assets are uploaded to the file cabinet, you can leverage the Bundle Builder to package the SSP application into a SuiteApp. Here's how to do it effectively:

Steps to Create a Bundle

Access the Bundle Builder: Navigate to Setup > Customization > SuiteBundler > Create Bundle when the SuiteBundler feature is enabled and you have relevant permissions.
Bundle Basics: Start by defining basic characteristics of your bundle.
Bundle Properties: Add descriptive details to help users understand and locate the bundle.
Select Objects: In Step 3 of the Bundle Builder, SSP applications will appear. Select the desired SSP application, which will include the SSP Application record and all its associated files.
Set Preferences: Review all bundle objects, applying preferences for how they should behave during installation and updates. You may lock objects to prevent changes in target accounts.
Finalize the Bundle: Set sharing options and review saved bundles as needed.

Important Considerations

When you install a bundle containing an SSP application in a target account, the entire SSP Application record and its files are copied to a dedicated application folder in that account’s file cabinet, accessible at:

/<Default Target HTML Hosting Root>/SSP Applications/<Application Publisher>/<Application Name>
Notably, since the 2019.1 version, updating a bundle that includes an SSP application does not automatically refresh script deployments in the target account. Existing deployments remain intact, meaning that users need to manually update Log Level and Status fields via the Script Deployment page if necessary.

Who This Affects

This bundling process is crucial for:

Developers: Those creating SuiteApps for various NetSuite accounts.
Administrators: Users managing application distribution and access permissions.
Account Managers: Facilitators ensuring that applications are correctly rolled out and managed.

Key Takeaways

SSP Applications can be bundled using the SuiteBundler for easy distribution across NetSuite accounts.
Locking applications prevents edits in target accounts, maintaining integrity.
Updates to bundles do not affect existing script deployments in the target accounts post-installation.

Frequently Asked Questions (4)

Do I need administrator permissions to create a bundle with SuiteBundler?

Yes, an administrator must enable the Create Bundles With SuiteBundler feature before you can access the Bundle Builder.

What happens to script deployments when an SSP bundle is updated?

Updating an existing bundle with an SSP application does not overwrite existing script deployments in the target account. The Log Level and Status fields remain unchanged.

Can I lock SSP application files in a bundle to prevent editing?

Yes, during the bundling process you have the option to lock certain objects to prevent unauthorized modifications in target accounts.

Where are the SSP application files stored after being installed in a target account?

The application record and files are copied to a designated folder: <Default Target HTML Hosting Root>: /SSP Applications/<Application Publisher>/<Application Name>.