- 2Installing Flosum
- 3Setting up Flosum integration user
- 4Connecting sandboxes to Flosum
- 5Setting up users in Flosum
- 6Setting org permissions
- 7Decide on naming convention
- 8Initialize the repository
- 9Setting up workflow permissions Application Development Flow
- 10Pulling changes from dev sandboxes
- 11Branching strategy
- 12Conflict and Merge strategy
- 13Static Code Analysis
- 15Regression testing
- 16Reference Architecture Integrations
- 18TFS/Azure Devops
- 19Git Integrations Compliance & Governance
- 20Compliance & Governance
As a best practice, for connecting your orgs to Flosum, we recommend creating a common user that can be shared by Flosum users as needed, such as when you connect your developer sandboxes, test sandboxes and production orgs to Flosum.
For example, if John Doe and Jane Smith are developers in your organization, we recommend creating a user "Flosum Integration" (firstname.lastname@example.org) in your production org. Once your sandboxes are refreshed that common user will be available in all your sandboxes.
This user should have Sysadmin privileges to enable Flosum to retrieve and deploy metadata components.