Workflows in error

[Mike Pokraka]

Hi Ravi,
It is only the workflow *template* that is version dependent. Tasks are
independent of your WF definition (they can exist in multiple flows) and
changes to individual tasks are like changes to ABAP code which become
effective imediately.
The only way to fix your problem is to reverse the change so the old flows
can continue and copy the task to a new one which you replace in your WF
(version dependent change).
There's a note out there on all this, search OSS for workflow version.
Cheers,
Mike

On Wed, July 4, 2007 8:25 am, Ravi Dixit wrote:
>  Hi WUGers
>
> We recently made a change to a workflow definition that was in the
> productive environment. We changed one of the tasks from Synchronous to
> Asynchronous with different object/method and outcome.
> As a result of this a number of workflows that in progress at the time of
> transporting the changes to production have gone into error and those that
> were triggered after that date are obviously working fine.
> My questions:
> 1. For the active workflows should it not continue to look at the
> definition
> at the time of creation or is it restricted by what you change.
> 2. The errors are appearing when it tries to create the next node after a
> user' decision step, is it possible to restart them in some other way as
> "SWPR - Workflow Restart After Error " does not work
> 3. Has anyone experienced such problems before and if yes what was done to
> resolve them?
>
> Regards
> Ravi
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>


-- 
Mike Pokraka
Senior Consultant
Workflow Connections
Mobile: +44(0)7786 910855