Workflows in error

[Mark Pyc]

G'day Ravi,

Did you change the Task or replace the Task with a new one in the WF
definition?

Workflows (WS) work with versions and instances continue to run under the
definition of the version they started under.

Tasks (TS) do not support versions. If you change a Task such that it's
signature changes (imports/exports) and move it up into a live
environment you're in trouble.

If you've created a new TS and referenced this in a new WF definition you
should be okay, but if you've modified an already called TS there isn't an
easy way out.

Please confirm which situation you're in.

Have fun,
Mark


On 7/4/07, Ravi Dixit <dolbydix at gmail.com> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070704/bff439df/attachment.htm