Sandbox app tokens perform differently depending on the configuration of App Lifecycle Management (ALM) for an app.
App configuration scenarios
When ALM is not enabled for an app, and a sandbox does not exist, the app token assignment process remains as it currently is:
- Navigate to the app token management page > Create an app token > assign it to an app - OR -assign an existing app token. The flow does not change
When ALM is enabled for an app, but a sandbox does not exist:
- Navigate to the app token management page from the live app >Create an app token > assign it to an app - OR -assign an existing app token. The flow does not change.
When ALM is enabled on an app, and a sandbox exists, there are two possible scenarios:
- If there are other existing change-sets on the review and publish page, and a user creates and assigns an app token in the sandbox, publishing the changes will also publish the app token assignment to the live app.
- If there are no existing change-sets on the review and publish page, the publish button will be disabled. If a user wants to publish an app token assignment, from sandbox to live app, then the user can assign the same app token that was created in the sandbox to the live app instead of needing to publish it.