Flow Naming Conventions

All prefixes are ALL CAPS. All Names after a prefix are CamelCase with no underscores outside of where indicated.

Meta-Flow Naming

  1. A Flow name SHALL always start by FL, followed by a number corresponding to the current maximum number of Flows in the Organization plus 1, followed by an underscore.
    • If the flow is specifically designed to be a subflow, it SHALL always start by SFL instead.
    • If the flow is specifically designed to be a scheduled flow that runs in Btches, it SHALL always start by BFL instead.
  2. A Flow name SHOULD always contain:
    1. the name, shorthand, or code of the business unit or process that led to its creation, for a Screen Flow
    2. the shorthand or code of the Object it is triggering from, in the case of a Record-Triggered or Scheduled Flow
  3. A Flow name SHALL be named after the action being carried out in the most precise manner possible.
  4. A Flow Description SHOULD always indicate what the Flow requires to run, what it does functionally, and what it outputs.

Flow Elements

DMLs

  1. Any Query SHALL always start by GET for any Objects, followed by an underscore, or FETCH for CMTD or Settings.
  2. Any Update SHALL always start by UPDATE followed by an underscore. If it Updates a Collection, it SHALL also be prefixed by ALL after the aforementioned underscore.
  3. Any Create SHALL always start by CREATE followed by an underscore. If it Creates a Collection, it SHALL also be prefixed by ALL after the aforementioned underscore.
  4. Any Delete SHALL always start by DEL followed by an underscore. If it Deletes a Collection, it SHALL also be prefixed by ALL after the aforementioned underscore.

Interactions

  1. Any Screen SHALL always start by C, followed by a number corresponding to the current maximum number of Screens in the current Flow plus 1, followed by an underscore.
  2. Any Action SHALL always start by ACT, followed by an underscore. If it calls APEX, it SHALL also be prefixed by APX after the aforementioned underscore. The Action Name SHOULD furthermore indicate what the action carries out.
  3. Any Subflow SHALL always start by SUB, followed by a number corresponding to the current maximum number of occurence of this Subflow within the main Flow plus 1, followed by an underscore. It SHALL also be prefixed by the flow's Name Code after the aforementioned underscore. 

Screen Elements

  1. Any variable SHALL always start by var followed by an underscore.
    • Any variable that stores a Collection SHALL always in addition start by coll followed by an underscore.
    • Any variable that stores a Record SHALL always in addition start by sObj followed by an underscore.
    • Any other variable type SHALL always in addition start by an indicator of the variable type, followed by an underscore.
  2. Any formula SHALL always start by form followed by an underscore, followed by the data type returned, and an underscore.

Logics

  1. Any Decision SHALL start by DEC if the decision is an open choice, or CHECK if it is a logical terminator, followed by an underscore. The Action Name SHOULD furthermore be prefixed by Is, Can, or another adverb indicating the nature of the decision, as well as a short decsription of what is checked
    • Any Decision Outcome SHALL start with the Decision Name without any Prefixes, followed by an underscore, followed by the Outcome.
    • The Default Outcome SHOULD be used for error handling and renamed ERROR where applicable.
  2. Any Assignment SHALL always start by SET, ASSIGN, STOREREMOVE or CALC (depending on the type of the assignation being done) followed by an underscore.
    • SET SHOULD be used for variable updates, mainly for Object variables, where the variable existed before.
    • ASSIGN SHOULD be used for variable initialization, or updates on Non-Object variables.
    • STORE SHOULD be used for adding elements to Collections.
    • REMOVE SHOULD be used for removing elements from Collections.
    • CALC SHOULD be used for any mathematical assignment or complex collection manipulation.
  3. Any Loop SHALL always start by LOOP, followed by an underscore, followed by the description of what is being iterated over. This can vary from the Collection name.
Type Name Description
do examples