Phased Upgrade of Managed Bundles

SuiteBundler supports a phased release process for managed bundle upgrades, similar to the release process for NetSuite upgrades. You can release a new managed bundle version to subsets of the install base, in phases, instead of having to upgrade the entire install base at the same time. You can maintain multiple versions of a managed bundle, because you can continue to push maintenance updates to accounts still using the older version of the bundle, during the time that other accounts are being upgraded to the new version.

Note:

You should not attempt to maintain more than two released versions of a managed bundle at any one time.

You can copy both a managed or a non-managed bundle to begin work on a new version, then deprecate the original bundle. However, the consequences of deprecating a managed bundle are different from deprecating a non-managed bundle.

Warning:

You should not remove a bundle from the copy chain while the older version of the bundle is installed by some users and that version is deprecated by a newer version of the bundle. Removing a bundle from the copy chain results into users not being able to install the latest version of the bundle. To understand the chaining of bundle copies, see Ancestry of Copied Bundles.

The following screenshots of the Bundle Availability page illustrate the differences in deprecation behavior for managed and non-managed bundles.

Deprecated managed bundles have the Edit, Push, and Upgrade Install Base options available in the Action menu on the Saved Bundles page and Managed Bundles page. Non-managed bundles do not have these options available on the Saved Bundles page.

Managed Bundles page with available actions highlighted.

Be aware of the following for upgrades to a managed bundle that has been deprecated:

For steps for upgrading a managed bundle, see Upgrading Your Managed Bundle Install Base.

Related Topics

General Notices