We’re Here to Help!!

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

Decide on naming convention

Follow

Release Management
Implementation Guide

Index

    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

Flosum recommends adopting naming conventions for the following entities:

  • Snapshots
  • Branches
  • Deployments
  • Component Name

 

Most likely you will have existing naming conventions you can adopt or extend to Flosum artifacts. Use names that reflect the contents or use of an entity. For example, branch names could be based on a change request number plus feature name. Deployment names could be based on the sprint cycle, feature name, change request number or a variety of other attributes. Snapshot names could reflect the nth day of the sprint cycle, feature name, or any other attribute.

In addition, it is possible to add new fields to capture custom attributes. This information could further be used for reporting and/or for automating workflows.

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

Comments