Workato and multi-site permissions

So, we are re-installing/re-testing a solution that we had mostly working before we upgraded to 2024.1. In the calls, you can set a site in the request settings. Previously, this seemed to work. This automation is doing cross site stuff, so we need it to be able to do that. However, now, Epicor seems to be ignoring this setting, and instead checking against a “Session” site. This is an automation user, and will be doing things with lots of different sites, so I can’t just change the site that it’s logged into and leave it.

I’ve run into this is 2 different BO’s now, (Reciept Entry, and now Job Entry). This seems like a fairly large oversight, so I’m wondering if I’m doing something wrong. Does anyone else have any experience with workato and multi site?

The workaround we seem to have to do is to create a pre-processing BPM and check the user, and if the user is our automation user, call the BO Ice.Session.Mod and set it there. But that seems odd that we would have to do that, when we are already working on setting the plant in the workato call.

3 Likes

I don’t know if this is related to your issue but the first release for an order line you create with automation studio is always created in the context of the session that the automation studio user last logged into no matter what you put in the request settings. I went back and forth on this for many months. Automation studio team says its not their fault, they are just calling the API. Epicor development says its working as designed, the release does not accept or honor explicit request settings. We have a bpm in place to correct it after the fact.

1 Like

https://epicor.ideas.aha.io/ideas/KIN-I-5361

Yeah, I’m having all kind of issues with site problems, lots of BO’s giving me problems. gross

1 Like