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

[Fred Lunaspa]

Hi Jocelyn,
 
Thank you very much! These guidelines are really practical/useful.
 
Regards,
 
Fred
 
>From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: AW: Workflow versioning: versions on development and producti
>on n ot the same
>Date: Mon, 7 Jul 2003 02:21:09 +0200
>
>Hi Fred,
>You don't need to keep them the same - the system will manage it - but do
>make sure you have applied all the relevant fixes/patches for the workflow
>transport system as sorting out the version issue had some problems in 4.6C
>early patches.  However yes do still make sure you create a new version
>each time you transport for safety's sake - especially in 4.6C.
>
>Also don't forget that if you are making significant changes it may be
>worthwhile copying your existing workflow and creating a new workflow
>number - i.e. create new workflow and decommission the old one.  For
>minor/incremental adjustments  versioning is fine, but for major design
>changes having a different workflow number also makes it easier to
>monitor/report on the impact of the changes.
>Regards,
>         Jocelyn Dart
>Consultant (SRM, EBP, Workflow)
>and co-author of the book
>"Practical Workflow for SAP"
>SAP Australia
>email: jocelyn.dart at sap.com
>phone: +61 412 390 267
>fax:   +61 2 9935 4880
>
>
>
>
>
>-----Original Message-----
>From: Fred Lunaspa [mailto:fredlunaspa at hotmail.com]
>Sent: Saturday,5 July 2003 12:30 AM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: AW: Workflow versioning: versions on development and
>production n ot the same
>
>
>Werner and Heinz,
>
>Thanks for your quick replies!
>
>I'm still figuring out what is the best way to 'manage' versions (keep them
>in sync on development/acceptance/production or not). The book 'Practical
>workflow for SAP' advises to always create a new version if a workflow is
>transported, to be sure the transported version is not overwritten per
>accident in the development system (this way the productive workflow can be
>tested in development). So I quess that's the way to do it. That means that
>if I want/need to keep the versions in sync, the highest version on
>development (not activated) must always be 1 higher than the active version
>on production. Again, if I want to keep them synchronized.......
>
>Regards,
>
>Fred
>
> >From: Werner Kv_l <werner.koessl at hirschvogel.de>
> >Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> >To: SAP-WUG at MITVMA.MIT.EDU
> >Subject: AW: Workflow versioning: versions on development and production
>n
> >ot the same
> >Date: Fri, 4 Jul 2003 14:30:30 +0200
> >
> >Hi Fred & Heinz,
> >
> >in all clients of our testsystem there is always only version 0000 at all
> >workflows.
> >But when we transport a workflow template into the productive system
> >a new version is generated (always!) indifferently if an instance exists
>or
> >not!
> >
> >Regards,
> >Werner.
> >
> >
> >-----Urspr|ngliche Nachricht-----
> >Von: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]Im Auftrag von
> >Schmidinger, Heinz (Unaxis IT BZ)
> >Gesendet: Freitag, 4. Juli 2003 13:59
> >An: SAP-WUG at MITVMA.MIT.EDU
> >Betreff: AW: Workflow versioning: versions on development and production
> >n ot the same
> >
> >
> >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|ngliche 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/
>
>_________________________________________________________________
>MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl
 
_________________________________________________________________
MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl