Releasing a SuiteApp Version
SuiteApps are made available on the SuiteApp Marketplace by releasing a version of the SuiteApp. To release a SuiteApp version, it has to be in the Pending state. For a SuiteApp to be available to users on the SuiteApp Marketplace, it must meet the publishing requirements. For information, see Requirements for SuiteApp Marketplace Availability.
Keep these constraints in mind when releasing a SuiteApp version:
-
Only two versions can be in the Released state at a time, one leading and one lagging. For more information, see SuiteApp Version Phases.
-
When you release the first version of a SuiteApp, it must be leading and can be any version number.
-
When you release the second version of a SuiteApp (and the first version was released as leading), the second version also has to be leading, and its version number must be higher than the first.
-
When releasing additional versions:
-
You can replace the previously released version by deprecating it. For more information about version states, see SuiteApp Version States.
-
You can make the previous version the lagging version, which replaces and deprecates the old lagging version.
-
After removing the SuiteApp from the SuiteApp Marketplace, the new version you release must have a version number higher than the last deprecated version.
-
To release a version as leading, its version number must be higher than both the last leading and last lagging release versions.
-
To release a version as lagging, its version number must be higher than the last lagging version and lower than the last leading version.
-
Releasing the version as lagging also deprecates the existing lagging version.
-
-
You can't release the first lagging version directly. To create it, release a new leading version and make the current leading version the new lagging version. After that, you can release lagging versions directly.
-
You can't release the same version twice. If you need to make changes, release a new version. You can also deprecate released versions at any time. For more information, see Deprecating a SuiteApp Version.
-
After your users click Upgrade for an unmanaged SuiteApp, they might see a choice of SuiteApp versions if:
-
Both SuiteApp versions support the account's current NetSuite version.
-
Both available versions are newer than the current SuiteApp version the account has installed.
-
The following diagram shows an example of choices you can make when releasing a leading 1.1 version while a leading 1.0 version already exists:
To release a SuiteApp Version:
-
Go to Control Center > My SuiteApps > My SuiteApps.
-
Do one of the following:
-
For a SuiteApp, click
and select Manage Versions. -
Click the SuiteApp name to view the SuiteApp details, then click the Versions tab.
-
-
In the Version column, find the SuiteApp version you want to release and click Release.
Keep the following in mind when releasing a leading or lagging version:
-
If you're releasing a leading version and one already exists, you can do the following options with the existing version:
-
Deprecate deprecates the current leading version.
-
Make Lagging makes the current leading version the new lagging version and deprecates the old lagging version.
-
-
If you're releasing a lagging version and one already exists, the current lagging version is deprecated.
To confirm, click Release in the Confirm Action popup window.
The SuiteApp version is released to the SuiteApp Marketplace, and the Status column is updated to Released. You'll see a confirmation that the release is successful.
Note:For a SuiteApp to be available to users on the SuiteApp Marketplace, it must meet the SuiteApp publishing requirements. For information, see Requirements for SuiteApp Marketplace Availability.
-
-
(Optional) If it's a managed SuiteApp, you can push the SuiteApp version to the install base. For information, see Pushing a SuiteApp Version Upgrade to Users.
-
(Optional) Click Done to close the SuiteApp details and go back to the My SuiteApps page.