Transport of Workflow templates in 46C

[Jody I. Chassereau]

Ravi,
 
I pretty much use OSS note 125400 as a guideline when making changes to a =
productive Workflow.  For most things, it seems like creating a new =
version of the template is the best and safest approach.  It should have =
no effect on the ones already running under the previous version in =
production.
 
However, if you change something like a container element definition or =
task import/export parameters, it might be used in both the old/new =
versions of the workflow.  For those type changes, they recommend copying =
and creating new tasks/workflow templates.
 
I haven't been bitten by a problem yet on production changes, so refer to =
the OSS note for further explanations.
 
Hope this helps.
 
Jody Chassereau
jichass at westvaco.com
 
>>> ravisap at yahoo.com 07/26/01 02:18PM >>>
Hi all,
    We have a production workflow which is version 0001. Somebody
modified it in DEV and replaced the version 0001 ( the changes were to
the workflow structure - so they are incomplatibale changes ). We
didn't move this to production - but what we did was created a new
version 0002.
   My question is if we transport this - will the transport also carry
the changes to the version 0001 and cause problems to the existing
instances of the production workflows ??
   We are on 46C.
   The only way left for us in case the transport carry chnages tot he
version 0001 is to copy the current template to a new WF template and
transport it - and not transport the old template.
 
Let me know if you have any suggestions.
 
TIA
Ravi
 
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/