Enhancement request: Break Inheritance Between a Recipe and the One it Was Copied From
The purpose of this ticket is to document our interest in this feature as a customer and be notified if this feature is released.
Currently, copying a recipe is the best way to avoid repeating a lot of manual steps to add common patterns like retrieving an object from a database, user from a directory, or monitoring for an error and performing a standard error handling set of steps.
Any recipe copied from another is assumed to be interested in upgrading a "a new version" of the original. This call to action is in bright orange, does not go away unless the action is taken, and is present every time the original is changed.
This is a useful tool for creating a sort of recipe lifecycle but unless recipes are developed in a very proscribed way, this also is a sort of visual nuisance at best.
The ability to dissociate/unbind two recipes from another would aid in avoiding any confusion.
Business Case: Until there is a sort of recipe template feature, copying recipes will be the most efficient way to avoid repetitive work in developing recipes that follow a common pattern. The ability to indicate that one recipe is not a candidate to receive updates/changes to the original recipe will aid in keeping recipes organized and intact, allowing users/operators with less familiarity with the recipe/Workato to safely maintain and run them.