Quick question for the community. We currently use Service Connect to bring orders over from our e-commerce site. It seems large orders take a long time, 100+ lines or more. A long time would be an hour or two. Some have told us this is par for the course with Service Connect as it mimics a user siting at a client workstation. Just curious what others experience working with Service Connect.
On a side note the servers involved are not maxed out on resource usage. Also our PLM traffic has the same behavior. And it does not matter the time of day when this occurs.
Service Connect workflows can be written very poorly… Who wrote yours? How old is it? SC is not the fastest thing in the world but an hour seems excessive
Agree completely with Jose. Service Connect IS slow, but you can make it crawl really fast with some poorly written workflows. I’ve seen workflows that do a GetByID on the entire order for every line. Sit down with a 100 line order in front of you and hit refresh 100 times, that’s the overhead the workflow is adding to it.
I know when we have orders with so many lines it even slows the client unless we change the Users SysConfig file. Though I have no idea if you can do that to Service Connect. Also agreed with others the SC can be a bit slow and poorly created workflows really can bring it to it’s knees.
It’s already covered, but I’d also support looking hard at the workflow. We’ve been through this, and many developers attempt to be too literal in “following what a user does at a workstation”. They will give you a workflow that mimics a user trace when there are far more efficient ways.
By comparison, I’ve yet to see a 100-line order come in from our website, but 30-line ones take 5-10 seconds for us, I think.
I know I’m late to this thread, but I’ve used DMT traces to simplify some of my code. It would work for ESC too. If you want to mimic something, do it from the DMT. It’s supposed to be the best known process for mass import.