Why would you version an Integration Procedure instead of cloning it?

Why would you version an Integration Procedure instead of cloning it?

• A. The new Integration Procedure will replace the existing one.
• B. The new Integration Procedure uses a Cache Block.
• C. The new Integration Procedure is Chainable.
• D. The new Integration Procedure will be used independently.

Answer: (A)

Versioning a Integration Procedure creates a new version of the same procedure so you can roll out updated logic without breaking existing implementations. The new version becomes the target for new requests, effectively replacing the old one for future usage, while the older version remains available for any existing integrations still calling it. Cloning would simply copy the procedure into a separate, independent item, which doesn’t automatically take over for new calls—you’d have to explicitly switch references to use the clone. So, versioning is used when you want an updated behavior to replace the old for new invocations while preserving the old version for ongoing use.

Versioning a Integration Procedure creates a new version of the same procedure so you can roll out updated logic without breaking existing implementations. The new version becomes the target for new requests, effectively replacing the old one for future usage, while the older version remains available for any existing integrations still calling it. Cloning would simply copy the procedure into a separate, independent item, which doesn’t automatically take over for new calls—you’d have to explicitly switch references to use the clone. So, versioning is used when you want an updated behavior to replace the old for new invocations while preserving the old version for ongoing use.