🕵️ Tips and Tricks from the Composer Team 🕵️‍♂️

Tip 15:  Composer Flow Naming and Migration/Environment /Version

Mulesoft Composer is an easy tool that can easily help you integrate systems together to support your business quickly. It is flexible and only comes in 1 instance for your organization. There’s no lower environments and the traditional migration/versioning process.

Here are some recommendations for naming your Composer Flow and implement a self-service migration/versioning strategy if you want to track the versioning and have multiple source/target system environments where you develop and test your flow before switching/activating in production.

Recommended Composer Flow Naming

TriggerType_DataType_Source_Target-Environment-Version

1. TriggerType - How the flow is triggered? Currently there are 2 methods; Event base or Scheduled. For example, EVT or SCH.
2. DataType - What data are you integrating? Something short and meaningful will be useful. For example, OpportunityWon-Lost.
3. Source - Name of the source system you are retrieving the data from. For example, SFOrg101.
4. Target - Name of the source system you are retrieving the data from. For example, SF-Slack-Sales.
5. Environment - For those that have multiple environments, you can append the environment names. For example DEV, TST, QA, PRD
6. Version - Version number of your flow. Do add a description on your flow to better identify the version changes

Here’s an example of a Composer Flow Name:

EVT_OpportunityWon-Lost_SFOrg101_SF-Slack-Sales-DEV-v1.2

Recommended Migration Strategy (If you have multiple environments)

1. Name your Composer Flow and append the environment name at the end. For example, EVT_OpportunityWon-Lost_SFOrg101_SF-Slack-Sales-DEV
2. You can connect this flow to your non-production environment for development and testing.
3. When you are ready to move to a higher or production environment, clone your flow and change the name to append the new environment name. For example, EVT_OpportunityWon-Lost_SFOrg101_SF-Slack-Sales-TST or EVT_OpportunityWon-Lost_SFOrg101_SF-Slack-Sales-PRD
4. You can version of your flow by appending the version number. For example, EVT_OpportunityWon-Lost_SFOrg101_SF-Slack-Sales-DEV-v1.2
5. If you need to make changes to this Composer flow, always start with the lowest environment to develop and test. You can then delete and re-clone (you’ll need to reconfigure your connections) or duplicate the changes in the higher environments.
6. This will give you a good catalog of your environments and versioning
   1. EVT_OpportunityWon-Lost_SFOrg101_SF-Slack-Sales-DEV-v1.0 - Inactive
   2. EVT_OpportunityWon-Lost_SFOrg101_SF-Slack-Sales-DEV-v1.1 - Inactive
   3. EVT_OpportunityWon-Lost_SFOrg101_SF-Slack-Sales-DEV-v1.2 - Inactive
   4. EVT_OpportunityWon-Lost_SFOrg101_SF-Slack-Sales-TST-v1.0 - Inactive
   5. EVT_OpportunityWon-Lost_SFOrg101_SF-Slack-Sales-TST-v1.1 - Inactive
   6. EVT_OpportunityWon-Lost_SFOrg101_SF-Slack-Sales-TST-v1.2 - Inactive
   7. EVT_OpportunityWon-Lost_SFOrg101_SF-Slack-Sales-PRD-v1.2 - Active