Distribution, upgrades, versioning
Installable Apps can be classified by where they were created and if/how they are intended to be shared
Distribution and upgrades
| Installable app type | Audience | Distribution | Upgrades | Uninstall |
|---|---|---|---|---|
| Local | 1 tenant only | None | From the My Apps menu your tenant administrator will be given the option to upgrade the app installation. If they do not do this, your tenant will remain on the previous version of the app | Local apps can be disabled, but can not be uninstalled from your tenant. The only way to remove this app completely is to delete the entire app in App Reg. |
| Private | Multiple tenant installations. Intentional and limited sharing and distribution | Share the Distribution Link found in App Reg > Basic Information > App Information with the tenant admins | Your tenant administrator will not know there has been an app upgrade unless the developer or app owner informs them. The app owner will need to provide the latest installation link after making changes. The tenant admin must uninstall the previous version of the app from My Apps before reinstalling again from the installation link. | Tenant admins can uninstall through the My Apps section of tenant settings |
| Public | Multiple tenant installations with a large audience. You want people to find and install your app on their own | Have been published to Seismic's App Catalog. Some public apps are free while some may require additional purchases, subscriptions, or services. For example, if you want to integrate Lessonly with Seismic, you'll need to make sure your organization has purchased Lessonly | Your tenant administrator will be given the option to upgrade the app installation from the My Apps menu in the tenant's system settings. | Tenant admins can uninstall through the My Apps section of tenant settings |
Versioning
App Registry handles all versioning on behalf of the developer.
Versioning is done on 3 different levels (e.g. 1.2.3)
Publication
When your app is published to the Exchange, it is given a new major version, resulting in a level 1 update.
- Example version 4.6.12 becomes version 5.0.0
Authentication scope changes
When you change your app's authentication, such as the Authentication Method or the Scopes, it receives a level 2 update. This also results in an update to your OAuth2 Information, including your client id and secret
- Example version 4.6.12 becomes version 4.7.0
App configuration changes
When you change your app's features, such as adding extension points or enabling events, it receives a level 3 update. You also receive a level 3 update when changing the name of your app.
- Example version 4.6.12 becomes version 4.6.13
App metadata changes
When you change superficial information on your app, like the description, owner's email address, or documentation URLs on the Basic Information tab, it does not result in a versioning update.
Updated 3 months ago