Manual intervention in a process flow (restart, retry or reroute): Part II
By Jean-Pierre Dijcks on May 22, 2007
Doing the actual "go back after I did something" is very simple. I've extended and changed the process flow used in the previous post (part I) to look like this:
Essentially I have some execution part (my silly procedure which insert yes into a table) which could be a mapping or set of mappings and then I have error handling. In this case if the procedure fails (for whatever reason, I can make this more sophisticated by going on error status or specific outputs) it goes into the manual activity. The administrator can come in to Browser and investigate the issue, resolve it and restart the process with the last execution.
In my example, I renamed the table to insert into, so I got the procedure to fail (imagine the select from an external table fails because the file does not (yet) exist). Go into the Browser and say Expedite Execution with a Status go OK and it tries the procedure again. Since I re-renamed the table it now works nicely...
Notice that at the highest level in the Browser this job is marked as OK but with some note that something went wrong at some point.
For the next entry in this series (didn't plan to do this, but hey all good things come in 3-s - Indiana Jones, Star Wars (ok 2 times 3) and of course Pirates of the Carribean...) we'll have a play with a mapping and commit control... that should be fun.