Re-Publishing Workflows with existing Process Instances

Yes - I thought about using the GoTo API call too, but it won't handle process instances with multiple workitems (the GoTo command only exists on the process instance object).

It's a difficult call.

You could, for example, have a server event on the end of every Activity within a workflow that checks a flag somewhere, and kicks off a new process instance for itself. The downside to this is each worklist item becomes a process instance - which is fine unless you have a workflow design that collects parallel processes back up at some point.
 

I'm not sure there IS a solution - it's a classic workflow problem. 

I think I've cracked this - and (after proving it in a rough prototype) will write it up for others to look at.

You can use the K2MNG to loop through all existing worklistitems, and record all their information elsewhere (your own database, for example). This is the easy bit.

The difficult bit - that I thought might be impossible - is how to recreate the process instances, each holding multiple worklistitems.

Here's what I'm building...

 
The Start Activity has a new line leading from it, with a condition in the line that a Process Property called "Flag" has "restart" written in it.

The new line leads to an activity called "Spawner". This has two lines leading from it - one that loops back on itself, and one that leads to another activity called "Mover".

Here's the theory...

1. We read our list of what previously existed for a process instance, and use it to control the looping through Spawner.

2. The loop line rule will return true as many times as is needed according to the number of worklist items needed.

3. The line leading to Mover will always be true - therefore generating a worklist item each time it loops.

4. The mover activity does a K2.GotoActivity() on each worklist item - putting it back where it was before the restart.

** Correction - Point 4 has to be done in software too - the ServerEventContext makes the whole thing move. The utility software will need to grab each worklistitem in the Mover Activity and move it through the K2ROM. 

5. We write a software utility to whiz through the new worklistitems and call Redirect() on them - putting them back with the user who originally had them.

The  process SOUNDS a lot more complex than it looks, but I believe it's the only sensible way of restarting process instances with multiple worklist items. It will work for Black Pearl too.