AW: Active Version of WF Template

[Becker Stephan (extern)]

=20
Brian, Brad,
=20
the workflow cannot switch versions at runtime for logical reasons, =
thus all
running workflows will always continue with the version they were =
started
with. To realise why this must be the case, imagine you have changed =
the
flow and the data that goes with it between versions, and a running =
workflow
would now try to switch from the old to the new version between steps, =
but
the running workflow does not have the data it needs to, say, evaluate =
a
condition in the new flow, because this was determined in a step of the =
NEW
flow that the OLD running workflow had already passed.. Even more =
basic, try
imagining how you would determine (putting yourself in the position of =
the
workflow engine) what the next step would be in the new version, coming =
from
the old version.. say the new version includes a few more activities =
and
branches, or even worse, the currently running step in the old flow =
does not
exist any more in the new flow.. as far as my understanding goes, it =
would
be a logical impossibility to describe such situations within the
constraints of any programming language.
=20
Greetings,
Stephan=20
=20
 
-----Urspr=FCngliche Nachricht-----
Von: Schroeter, Brad [mailto:BSchroeter at ti.com]
Gesendet: Dienstag, 26. Februar 2002 23:49
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Active Version of WF Template
 
 
Brian,
I'm on 4.0B and I believe that's the way SAP works by design so that =
"old"
workflows will not possibly error out due to changes in the workflow
template (any new workflows created after the transport/activation =
should
use the new workflow version).
=20
-Brad=20
 
-----Original Message-----
From: Snyder, Brian [mailto:BSnyder at wafertech.com]
Sent: Tuesday, February 26, 2002 3:38 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Active Version of WF Template
 
 
 
I have a WF(46C) that is initiated when an employee has a new =
qualification
added to their training profile.  This WF then waits until the =
qualification
expires and then sends an email to the employee.  I have just made some
modifications to the original WF template and transported it to =
production.
When I look a the log for existing WFs that are "In Process", they =
appear to
be using the OLD version of the template.  I activated the WF in =
production
but they still appear to be using the OLD version when I look at them =
in the
WF log. =20
 
Did I miss something?  Is there any way to get the IN PROCESS work =
items to
use the new vesion of the WF?=20
 
Any help would be appreciated!=20
 
Brian Snyder=20
WaferTech=20
360.817.3141=20
bsnyder at wafertech.com=20
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20020227/69a0fd3b/attachment.htm