topic Re: How do you handle multi-recipe connection change? in Workato Pros Discussion Board

How do you handle multi-recipe connection change?

mroldanvega — Mon, 18 Oct 2021 20:02:08 GMT

We have a project that is composed of 7 recipes all together (including callables, scheduled, and MS Teams). When we finish the dev, we want to connect them to our Salesforce QA environments. Today, we have to go to each recipe and change the connection from Salesforce Dev to Salesforce QA.

It would be useful if there was a way for us to change the connection for all the recipes at once, without having to go one by one.

Any ideas or other suggestions?

Re: How do you handle multi-recipe connection change?

justinmnorris — Mon, 18 Oct 2021 20:08:14 GMT

Hey Manuel, I agree this is a pain.

The only solution I'm aware of is if you are using multiple Workato environments for your different lifecycle stages (e.g., Dev, QA, Prod) then Workato can automatically switch the connections for you when you import to the new environment:

https://docs.workato.com/recipe-development-lifecycle/import.html#import-status-tags

"When importing a package, Workato will attempt to automatically fill in connection details with existing connections in the importing account. Workato checks that this connection type exists and that there are no multiple connections of that type (for example, multiple Gmail accounts). If these conditions are met, the connections required in the imported recipes will be configured automatically. If this is not possible, then you may need to manually re-establish connections needed by the recipes after import."

Re: How do you handle multi-recipe connection change?

br00578505 — Mon, 18 Oct 2021 20:14:01 GMT

If we have more than one environment then pretty simple. In case have only one environment manually have to promote the recipes. Do not expect secutiry without having additional work.

Re: How do you handle multi-recipe connection change?

br00578505 — Mon, 18 Oct 2021 20:14:59 GMT

Yes, as Justin said more environments available then pretty easy.

Re: How do you handle multi-recipe connection change?

mroldanvega — Mon, 18 Oct 2021 20:38:53 GMT

Yeah, if there are multiple environments then it is easy to change it with the RLM feature, but if in the same environment, then this is painful.

Do you guys suffer from this often, or is it just us?

Re: How do you handle multi-recipe connection change?

justinmnorris — Mon, 18 Oct 2021 20:46:02 GMT

Yep same here. I think environments is the way to go although they are not inexpensive to add on last I checked.

Re: How do you handle multi-recipe connection change?

steven-marissen — Mon, 18 Oct 2021 21:15:48 GMT

It's a logical transition from an easy to start single environment and then move towards a machine of multiple environments, multiple teams etc as you scale.

It does have a learning curve (technical and organizational wise) but once you get used to multiple environments, it is definitely worth it. We are still on that track 🙂

Do consider that you may need to rework some recipes if they weren't built for this for example: usage of properties, lookup tables, ... instead of "hardcoding".

Re: How do you handle multi-recipe connection change?

mroldanvega — Mon, 18 Oct 2021 21:41:30 GMT

OK, so it looks like this is not a general pain.

Do you all have a single connection for each application on each environment? E.g. Only one connection to Salesforce.

my use case was for one you have multiple connections in the same environment, but it doesn't look like many of you do have them.

Yeah, we've been learning to leverage more properties to support multi-environment setup. It has been interesting, but make the deployment so much easier and less prone to error.

Re: How do you handle multi-recipe connection change?

deven-maru — Tue, 19 Oct 2021 02:09:24 GMT

Manuel Roldan-Vega how many Salesforce connections do you have in the scenario you described above? Are these connections using different users/credentials or same?

Re: How do you handle multi-recipe connection change?

mroldanvega — Tue, 19 Oct 2021 02:23:26 GMT

We have 3. Yes, all have different credentials for different Salesforce Orgs.

Re: How do you handle multi-recipe connection change?

deven-maru — Tue, 19 Oct 2021 02:43:41 GMT

Thanks Manny. We are looking into connection mapping feature during deployment. Mainly to support dev to stage to prod connection setting so you don't have to set it manually in individual environments after deployment.

Re: How do you handle multi-recipe connection change?

mroldanvega — Tue, 19 Oct 2021 02:48:03 GMT

Thats great news, Deven. Look forward to it.

Re: How do you handle multi-recipe connection change?

ajorde — Tue, 19 Oct 2021 06:59:47 GMT

I have 4 teams to represent my environments (dev, qa, stage, prod) and then I have a connection named Salesforce in each team with the connection made to the relevant Salesforce environment.

You could theoretically export your recipe package, change the json in the files to use the name of the next environment and reimport. It sounds like it would be a pain to retest again in the lower environment though.

Or.. you could possibly do something like this with Projects - create a dev and qa project, export from the dev project, update the json in a text editor to point to Salesforce QA connection, and import to the qa project. It would create multiple copies of recipes so might still be a lot to manage. You'd also probably want to make sure to have a recipe ops recipe turning off active recipes so your costs don't get out of control.

Re: How do you handle multi-recipe connection change?

mroldanvega — Tue, 19 Oct 2021 07:50:46 GMT

Thank you, Amy Jorde.
So you have connections to the same app on different projects or teams?

Re: How do you handle multi-recipe connection change?

ajorde — Tue, 19 Oct 2021 07:55:53 GMT

Correct. In my Workato Dev team, I connect to Salesforce Dev environment and call the connection Salesforce. In my Workato QA team, I connect to Salesforce QA environment and call the connection Salesforce. Then when I export from my Workato Dev team and import into my Workato QA team, it's the same set of recipes and I don't make any change in Workato QA environment, but it's hooked into the Salesforce QA environment. This might be the way our contract with Workato is structured that we have a separate team per environment but I don't think I could manage it very well otherwise.

Re: How do you handle multi-recipe connection change?

mroldanvega — Tue, 19 Oct 2021 08:06:16 GMT

Wait... what do you mean by Team?
Team=Environment?

Re: How do you handle multi-recipe connection change?

ajorde — Tue, 19 Oct 2021 08:24:59 GMT

Team = Environment before Workato's new Environment functionality is released (this quarter or next quarter - I don't remember which), but it's a different workato functionality. About 5 minutes into this video, they explain it: https://docs.workato.com/recipe-development-lifecycle.html#recipe-lifecycle-management

in the new UI, to switch teams, you click on the top left and it looks something like this: