February 2024

App and Solution Onboarding and Gating Updates

6min
overview we have added several new capabilities to app and solution onboarding apis, enabling developers to onboard their apps and solutions to production type tenants faster in addition, we have introduced necessary gatings to prevent human errors such as onboarding of an app or solution in development state to production type tenants summary of updates apps and solutions onboarding to prod type tenants developers can now use the updated onboarding apis to onboard their apps and solutions to production type (customer facing) tenants developers can choose to onboard to a single tenant or list of tenants or to all tenants within a stack stack onboarding for apps and solutions developers can also onboard their apps or solutions to all tenants in a stack by using a single api call, reducing the time required by developers for onboarding automatic subscription update app and solution onboarding now automatically updates the subscriptions to use latest version, eliminating the need to call a separate subscription api call after the onboarding credential type override the stackcredentialoverwrite attribute in the app and solution onboarding api enables the developers the use of production credentials while onboarding to apps or solutions to development/staging type tenants gating policies the new gating policies ensure that only fully validated apps and solutions get onboarded to production tenant environments, preventing issues for end users updates include state based gating apps and solutions must be in a live state to be able to onboarded to production tenants additionally, solutions can only go live only if all apps within them are live role based gating only product admins can publish apps/solutions live additionally, only developer admins and product admins can onboard apps and solutions to production type tenants ownership based gating only app developers from the organization that own the app can upload aaa permission files within a tenant, this is done to prevent any accidental overwriting of incompatible permissions files