Work on a User Story on a Salesforce CI/CD project
Work in your org
Once your User Story is started, you work in your dev sandbox or scratch org like in any other org: Salesforce Setup for configuration, VS Code for code. A few guidelines make the life of the release manager easier and avoid regressions when your work is deployed to the other orgs.
- Open your org: open the org linked to your User Story from VS Code.
- Configuration guidelines: API names, access management, Flows, hardcoded Ids, images, user references.
- Profiles and Permission Sets: why Permission Sets come first, and the Profile attributes that need special care.
- Development guidelines: push and pull code between VS Code and your org.
- Install packages: register the packages installed in your org so the CI server installs them everywhere.
- Deployment actions: declare the steps that must run before or after the deployment of your User Story (data loads, Apex scripts, Experience Cloud publishing, scheduled batches, manual steps).
When you are done, publish your User Story.
If your colleagues merged changes in the meantime, Backpromote (Beta) brings them into your dev sandbox so you work on an up-to-date org.
Video walkthrough
This recording shows how to work on a User Story in a source-tracked sandbox. It was recorded with the previous interface of the extension: the screens have changed, the steps have not.