The configuration steps differ between FSC Branch Management and Git Branch Management. The right approach depends on which meaning applies to your project.
- For FSC: enable Financial Services Cloud Retail Banking
Setup, FSC Settings. Enable the Retail Banking modules and assign the permission sets to bankers and branch managers.
- For FSC: create Branch records and hierarchy
Model branches, districts, and regions as records linked through parent lookups. Assign bankers and customers to branches.
- For FSC: build branch dashboards
Surface Activity, Pipeline, Goal Attainment, and Coverage dashboards per branch and roll them up to district and region.
- For DX: define a Git branching strategy
Choose trunk-based, GitFlow, or environment-based. Document the policy, protected branches, and CI gates.
- For DX: align branches with the org chain
Map dev sandboxes to feature branches, UAT to integration branch, staging to release branch, production to main. CI/CD deploys to each environment from the corresponding branch.
- Disambiguate the meaning before reading documentation. FSC Branch Management and Git Branch Management share a phrase, not an implementation.
- FSC Branch hierarchy lookups can break if branches are reorganised mid-quarter. Plan reorganisations against the financial calendar.
- Git branching strategies that do not match team size cause friction. Trunk-based works for small teams; GitFlow scales to larger ones.
- Salesforce metadata does not merge cleanly across branches. Protected-branch rules and PR validation reduce the pain.