ARCHIVED - Process Builder Naming Conventions

Process Builder is old, decrepit, and deprecated.
You can't create new ones, and if you're editing old ones you should be migrating to Flows instead.
This is ARCHIVED content, will never be updated, and is here for history reasons.

1. A Process Builder name SHALL always start by PB, followed by a number corresponding to the number of process builders in the Organization, followed by an underscore.
   a. If the Process Builder Triggers other Process Builders, it SHALL always start by TPB instead.
   b. If the Process Builder is Invoked by other Process Builders, it SHALL always start by IPB instead.
2. The end of a Process Builder name SHOULD always be:
   • the name of the object, in the case of a Triggering Process Builder (TPB)
   • the action carried out, in the case of an Invoked Process Builder (IPB)
   • the trigger and action, in the case of a standalone Process Builder (PB)
3. A Process Builder name COULD contain either C, CE, or CES wrapped by underscores, to show if the PB triggers on Creation, Creation and Edition, or Subsequent Modifications that Fill Criteria. The default assumed setting is CE if none is written. *3
4. All Process Builder Triggers MUST have a description detailing their purpose.
5. A Process Builder Decision Diamond SHALL be named after the criteria that are used in the most precise manner possible.
6. A Process Builder Action SHALL be named after the action being carried out in the most precise manner possible.