Cloning an Integration Procedure creates a new, distinct procedure that is completely independent of the original. This is the appropriate action when the new procedure is intended for a separate business process or requires a different lifecycle management path (e.g., a different Type and SubType). Versioning, by contrast, is used for iterative development on the same procedure. A new version maintains the same Type and SubType and is intended to eventually replace the previous active version for all callers of that specific procedure. Therefore, if the new procedure must be used independently, it must be a clone.

1. Salesforce Help

OmniStudio Documentation

"Integration Procedure Versions and Clones": This official documentation explicitly differentiates the two actions. It states

"Create a version when you want to modify an Integration Procedure and eventually replace the older version." For cloning

it implies creating a new

separate procedure

often to be used as a template for a different purpose. The core concept is that a clone becomes an independent asset.

2. Salesforce Help

OmniStudio Documentation

"Create a Version of an Integration Procedure": This guide details the process of versioning for making changes to an existing procedure that will be part of the same lineage. It notes that the Type and SubType are carried over

reinforcing that it's the same logical procedure.

3. Salesforce Help

OmniStudio Documentation

"Clone an Integration Procedure": This document describes cloning as the method to "create an Integration Procedure based on an existing one." This is done to create a new

independent starting point

which directly supports the rationale for using it independently.