SuiteApp Versions
A SuiteApp version is a specific version of your SuiteApp. You can release a SuiteApp version to the SuiteApp Marketplace and push it to users. You can view all versions of the SuiteApp from the version history. For information, see Viewing the SuiteApp Version History. To be available to users on the SuiteApp Marketplace, the SuiteApp must meet the SuiteApp publishing requirements. For information, see Requirements for SuiteApp Marketplace Availability.
You can create multiple versions for a SuiteApp, but only one version can be in the Released state for each phase at a time. To create a new SuiteApp version, see Creating a SuiteApp Version.
The following diagram shows the SuiteApp version state workflow and available actions:
For information about the available states and actions, see SuiteApp Version States and SuiteApp Version Actions. For information about phasing SuiteApp versions, see SuiteApp Version Phases.
SuiteApp Version States
SuiteApp version states show up in the SuiteApp version history. Here are the possible states for a SuiteApp version:
|
State |
Description |
|---|---|
|
Deprecated |
A Deprecate action was performed on the SuiteApp version and it's no longer available on the SuiteApp Marketplace for users to install. See Deprecating a SuiteApp Version. |
|
Pending |
The SuiteApp version has been created, but it isn't yet available on the SuiteApp Marketplace for users to install. See Creating a SuiteApp Version. If a release attempt fails, the version remains in the Pending state. |
|
Released |
The SuiteApp version is available on the SuiteApp Marketplace for users to install. See Releasing a SuiteApp Version. For managed SuiteApps, the version can also be pushed to users. For information, see Pushing a SuiteApp Version Upgrade to Users. |
SuiteApp Version Actions
You can perform actions on a version from the Action column in the SuiteApp version history.
Depending on the state, you can do one or more of the following actions on a SuiteApp version:
|
Action |
Description |
|---|---|
|
Delete |
You can delete SuiteApp versions in the Pending state. A deleted version is removed from version history. For more information, see Deleting a SuiteApp Version. |
|
Edit |
You can edit SuiteApp versions in the Pending state. For more information, see Editing a SuiteApp Version. |
|
Release |
You can release SuiteApp versions in the Pending state. For more information, see Releasing a SuiteApp Version. |
|
Deprecate |
You can move SuiteApp versions in the Released state to the deprecated state so they’re no longer available on the SuiteApp Marketplace. For more information, see Deprecating a SuiteApp Version. |
|
Upgrade Install Base |
Managed SuiteApp versions in the Released state can be pushed to users of the SuiteApp.
Note:
This action:
For more information, see Pushing a SuiteApp Version Upgrade to Users. |
SuiteApp Version Phases
SuiteApp version phasing is a way to support two release streams of a SuiteApp by separating the install base into the following upgrade phases for different SuiteApp versions:
-
The Leading phase is the newest release stream of the SuiteApp. Leading versions are released as the latest available version of the SuiteApp.
For example, the leading SuiteApp version might use a new NetSuite functionality and set a minimum NetSuite version of 2019.1. After all of your customer accounts are upgraded to 2019.1, all of your SuiteApp users can be upgraded to this leading SuiteApp version.
The leading SuiteApp version can go through several versions, as your SuiteApp is enhanced and bugs fixed.
When a leading release version is replaced, the old leading version can be deprecated or converted to the lagging release version.
-
The Lagging phase is the pre-existing release stream of the SuiteApp that will eventually be replaced by the leading release stream.
For example, the lagging SuiteApp version might use a pre-existing NetSuite functionality and set a minimum NetSuite version of 2019.1.
The lagging SuiteApp version can go through several versions, as your SuiteApp is enhanced and bugs fixed.
You can use SuiteApp version phasing to ensure smooth distribution of your SuiteApp during the NetSuite phasing period where some of your users are on different versions of NetSuite. Matching your SuiteApp phasing to NetSuite release phasing provides you with a way to make use of new NetSuite functionality in your SuteApps while still supporting users of the older SuiteApp whose accounts have not yet been upgraded. You can control what accounts have each version of the SuiteApp.
You can also phase your SuiteApp versions for the same NetSuite version. For example, both your leading and lagging SuiteApp versions can require NetSuite 2018.1. This is useful if you want to test bug fixes on a subset of your install base before rolling them out to everyone.
You can see the currently released leading and lagging versions on the My SuiteApps page, the Version History page, and under Versions in the navigation pane of the SuiteApp details.
For information about how the version phase affects releasing a version, see Releasing a SuiteApp Version.
The following illustration shows an example of SuiteApp versions that make use of the leading and lagging phases:
In this example, 25% of the install base are on version 2.0.0 in the leading phase, receiving the latest features in the SuiteApp, while the remaining 75% of users are still on the 1.0.0 version that was made lagging during the 2.0.0 version release. Fixes continue to be released on the lagging phase while development of features and fixes proceeds on the leading phase. By version 2.0.3, all users are on the leading phase, and version 1.2.0 in the lagging phase is deprecated.
For information about working with SuiteApp versions, see the following topics: