Share
Report
1,000We have several different order types that run the same 3 sequential custom order steps immediately after a shipper's "Release for Update" and before "Update Shipper"; these custom order steps are stored procedures. Each order step mentioned is set to invoke automatically and none of these order steps is credit checked.
About a third of the time, the shippers get "stuck" on the second stored proc. By that I mean that - through process manager - the shipper processes "Release For Update", and then processes "Custom Stored Proc 1", but then it leaves the shipper with the NextFunctionID/NextFunctionClass set to the order step where it should process Stored Proc 2 - and stops.
So unless we retrieve the "stuck" shipper in the shipper screen, and hit "Next", the shipper doesn't move on to the next order step which is custom Stored Proc 3. Pulling each shipper up is very time consuming!
My staff is resisting turning these stored procs into a single stored proc because not all order types require all of the steps.
So I've been trying to figure out if we could insert an order step into the process queue, and I can see how we could easily do that. The problem is that I've been testing various "Process types" and none of them work to move these custom stored procs on to the next step when run through the process manager's process queue. I've tested process types PRCSH & UPDSH.
Does anyone have any ideas about how we can get the shppers to move on to the next order step?
Thanks in advance.
*This post is locked for comments
All responses (
Answers (
