Detaching Recipes

Hi had discussed this with Gautam at Dreamforce 2016. You should be able to detach recipes from their origin if they are based on another recipe. There is no advantage but significant risk now to accidentally "update" and kill your enhancements.

Amanda Wong

said about 4 years ago

There is actually no risk when you update your recipe to a new version of the original recipe by mistake. With Workato's version control abilities, you can always restore your recipe to an older version.

To do this, in your recipe view:

1. Click on the tab Versions

2. Click into an older version of the recipe you would like to restore

3. Click on the button Restore this version at the top right corner

Meanwhile, if you would like to follow a related topic on controlling automatic notifications about version upgrade of copied recipes, please click here.

RK

said about 4 years ago

Yes, but at some point it just makes no sense to keep the link. There is no versioning, so it's even impossible to tell what new changes would have been incorporated. As I said, I spoke with Gautam - check with him, he understood entirely why this is a good idea.

Jeremy Farber

said almost 4 years ago

I agree on being able to understand what was changed. If you hit save a lot like I do you very quickly get a lot of versions and it's impossible to get back.

Amanda Wong

said almost 4 years ago

Understood your rationale. Meanwhile, there is a simple workaround to detach recipes -- you can break the recipe connection to parent with the following steps:

1. Copy the recipe you want to use ---> You get Copy of Recipe

2. Make a copy of the copied recipe (first copy) ---> You get Copy of Copy of Recipe

3. Delete the copied recipe (first copy) and use the second copied recipe ---> Keep Copy of Copy of Recipe, Delete Copy of Recipe

The resulting recipe will not be tagged under another Parent recipe.

Still can't find your solution?

Send us a ticket, we will try our best to assist you with your problem