We’re Here to Help!!

Find A Solution, Learn Best Practices & Get Support 24x7

Compliance & Governance


Release Management
Implementation Guide


    Core Setups
  • 1Overview
  • 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
  • 14Apex
  • 15Regression testing
  • 16Reference Architecture
  • Integrations
  • 17Jira
  • 18TFS/Azure Devops
  • 19Git Integrations
  • Compliance & Governance
  • 20Compliance & Governance

Most customers review the implementation of Flosum with their business teams as well as the compliance teams. One of the common trends observed in Flosum implementation is that more and more customers are involving their business in making changes to their applications. We highly recommend to involve your business teams, executives as well as compliance teams to improve your governance.

Most customers will implement specific logic or extend Flosum to ensure that their internal processes are being followed. Here are some examples of how customers use Flosum from a governance perspective:

  • For example, many customers will have the approval process before the code changes are committed to the repository.
  • In other cases, we have seen that most customers will have their own custom validation logic before changes are getting deployed to the upstream organization such as the staging and production organizations.
  • Customers use the audit trail feature to review and report manual changes in production environments.

It is vital to work with your business counterparts, executive management and compliance management during the implementation of Flosum.

Print Friendly and PDF
Was this article helpful?
0 out of 0 found this helpful