02-13-2018 05:33 AM
OK we are running K2 Five (5.0001.1000.1).
In 4.7 we could call an IPC process as part of a loop or use plan per slot (no destinations).
The sub-workflow / IPC process would have a task in it and we could then add a succeeding rule to stop the parent process continuing before all the sub-workflow tasks were completed.
How the devil is this accomplished in the new workflow designer for Five?
I can see the loop activity and the sub workflow activity and see that you can stop the workflow continuing until the sub-workflow task has completed but if you check this then you cannot do the looping as it'll create the first task and then wait. I think this was the same feature as the synchronous option in 4.7.
Solved! Go to Solution.
02-13-2018 05:56 AM
There is a Sub Workflow For Each feature that is high on the backlog for later this year that will provide the same level of functionality that was previously achieved using the plan per slot no destination rule option but done in a way that is easier to understand and configure.
02-13-2018 06:57 AM
So is there a workaround to stopping the parent workflow continuing?
Maybe a creating a task after the loop has completed which can then be completed by the child process?
02-13-2018 08:01 AM
A task could work but you might look into the "Wait For External System" option that is available on the SmartObject step which behaves like an async server event. Basically you can save a Serial Number to a SmartObject using the SmartObject step and have that step wait until the sub workflow finishes it by using the serial number. Here is the help doc that talks about the async option: http://help.k2.com/onlinehelp/k2five/userguide/5.0/default.htm#K2_Workflow_Designer/Use/Toolbox/Smar...
02-14-2018 06:02 AM
Thanks - struggling to see how to start/action the Smart Object that's now waiting.
It says I need to do this manually through the Workflow API, which API does it refer to and is there not a SmartObject method or endpoint I can call without writing code?