Hello experts.
I have a few different questions in my current project related to Canvas apps and their ALM/deployment process.
So we have Dev -> Test -> Prod env. The deployments are automated in Devops and we use Managed solutions in Test and Prod.
1. First question is about adding new functionality in the Dev env for the Canvas App. Say there are other parts of the solution that needs to be deployed to Prod, but I want to keep new Canvas app functionality in Dev, how should I best handle this? Which code is being sent to Prod, the "saved" version in the Canvas app or the "published/live" version of the Canvas app?
1b. If it is the published version that is sent to Test and Prod env through the deployments, do we just need to have this in mind, that we only save and not publish when developing new features that should not be sent to Prod? Or is there a better way...
2. Yesterday I tried to Edit the Canvas app in the Prod env, and it worked to change the code and publish it. Is this how it is supposed to work, even though it is in a Managed solution?
3. Any other thoughts about best practices regarding the deployment process of Canvas apps that are good to implement or consider. Appreciate any inputs. Thanks.

Report
All responses (
Answers (