AW: Workflow versioning: versions on development and production n ot the same

[Schmidinger, Heinz (Unaxis IT BZ)]

Hi Fred,
 
this is a result ogf the policy of versioning WF's.
 
If an intsnace of a WF defintiion exists in a System (in any client), a =
new
version is generated after transport else the existing version is
overwritten.
The think to rember that there exists a oss-note to this issue.
 
maybe it helps.
 
Regards
 
Heinz
-----Urspr=FCngliche Nachricht-----
Von: Fred Lunaspa [mailto:fredlunaspa at hotmail.com]
Gesendet am: Freitag, 4. Juli 2003 13:55
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Workflow versioning: versions on development and production =
not
the same
 
Hello,
 
I found out that the workflow versions on development and production =
are not
(always) the same. In some cases the version on development is lower =
than on
production, sometime vise versa. I know that when transporting a =
workflow to
production the system creates a new version of the workflow. Also I =
know
that it is recommended to create a new version on development after
transporting a workflow.
 
My question is: should I bother keeping the versions on development and
production alike, or not?
 
If yes, how can I do that? In case the version on development is lower =
I can
create 'dummy' versions that are added to transport requests that must =
not
be transported to production (otherwise the system adds a new version =
on
production and the versions are again not the same). In case the =
version on
development is higher I do not know what to do...
 
Regards,
 
Fred Kouw
 
_________________________________________________________________
Hotmail en Messenger on the move
http://www.msn.nl/communicatie/smsdiensten/hotmailsmsv2/