How to get ack to Old version of workflow template

Thu Dec 21 09:24:55 EST 2006

Mike,
Thanks for the clarification!!  
We are a small workflow team, so we keep things simple by keeping just
'000' in dev and communicating thoroughly about our changes, but it is
enlightening to see the possibilities for others with more complex
teams.
Cheers & Happy Holidays,
Sherie

Sherie Munday
Workflow Developer & Analyst
Air Products & Chemicals, Inc. 

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Gambier
Sent: Thursday, December 21, 2006 5:04 AM
To: sap-wug at mit.edu
Subject: RE: How to get ack to Old version of workflow template

Subashi, Sherie,

A word of caution on WF Versions: as far as I know, although I'm
prepared to be corrected on this, the container is NOT version
controlled so be very very careful about mixing changes. It's very easy
to assume that version Management in Workflow is the same as it is in
ABAP and rolling back changes or jumping between versions is a piece of
cake, unfortunately it is not. 
It's about 90% effective really.

If you have deleted any container elements or changed the nature of
existing elements I recommend you double-check the production version
closely and make sure you are 100% confident the changes will not affect
any live instances because they will be immediately affected by your
changes.

Adding new elements should be fine provided those elements are entirely
new and not used by any steps in previous versions of the definition and
of course they must syntax check (new elements based on data types or
objects left behind in development will cause activation errors in your
definition).

You can create 'new' versions of WF definitions in development (so you
don't actually have to be working on the same version all the time, or
indeed continuously update version '0000'). I have found this to be
particularly useful if I am adding or removing entire blocks and
therefore significantly changing the definition as it cleary shows to
someone else how the definition has evolved. But be sure to activate
your new version before you start, otherwise you may fool yourself into
thinking you are then changing your new version when you may not be at
all.

Sometimes as an extra precaution, should I forsee the need to manually
undo things, I print off the definition from SWDD as a hard copy (how
old school?), so at least I have an idea of the sequence of things
before I start to change them.

For most other defintiion changes if somebody has changed the same
definition as you but their Transport was released in your development
environment BEFORE you managed to make any change, then you should be
covered by the Transport mechanism at least, which will have taken a
snapshot of the definition table entries as they were. But, if you
managed to change the definition and their Transport was released
AFTERWARDS (perhaps you added your changes to their Transport) you'll
find that your changes will have been dragged along, whether you wanted
them to or not.

We have adopted the practice of 'protecting' our Transports in
development to avoid other developers tacking on their changes to
objects unintentionally like this. You may want to do the same.

MGT

>From: "Munday,Sherie J." <MUNDAYSJ at airproducts.com>
>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>Subject: RE: How to get ack to Old version of workflow template
>Date: Wed, 20 Dec 2006 13:54:15 -0500
>
>Subashini,
>I have a little different spin on your question...
>
>If all of the other person's changes were made prior to yours and his 
>transport is separate from yours, then certainly his can move without 
>yours.  When your changes/transport moves at a later date, it will 
>create the next version in that next system.
>
>However, if you have both been making changes, saving, activating and 
>making transports to the same template in dev, then they are mixed 
>together in the same version.  In development there is only one version

>... 000 and presumably you have both been making changes to that 
>version. If this is the case, and his are ready to move to production, 
>you will need to back out/remove your changes or he will have to wait 
>until yours are ready for production.
>Best Wishes,
>Sherie
>
>Sherie Munday
>Workflow Developer/Analyst
>Air Products & Chemicals, Inc.
>
>
>-----Original Message-----
>From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On 
>Behalf Of Shrestha, Bijay
>Sent: Tuesday, December 19, 2006 8:50 PM
>To: SAP Workflow Users' Group; sap-wug at mit.edu
>Subject: RE: How to get ack to Old version of workflow template
>
>Hi Subashini,
>
>First you should generate and release the correct and ready version to 
>Prod. Then in Dev. environment you can retrieve the old version by 
>clicking on other version in Workflow Builder. Then you can keep making

>changes.
>
>Bijay Shrestha
>Sr. Consultant
>Pragmatek Consulting Gr.
>
>	-----Original Message-----
>	From: sap-wug-bounces at mit.edu on behalf of 
>Subashini.Bhoopathiraj at uinet.com
>	Sent: Tue 12/19/2006 6:59 PM
>	To: sap-wug at mit.edu
>	Cc:
>	Subject: How to get ack to Old version of workflow template
>
>
>
>	Hi all,
>
>	  I have made some changes to the workflow template, another
person 
>also made the changes to the same workflow template, but my changes not

>yet tested, so it shouldn't move into production.
>
>	  But other person's changes should move in Production with out
my 
>changes . I thought of activating Old version & other person can do the

>change & transport to PRD. after that i can retrive my version & 
>transport to the production. How can i do this??
>
>	Thanks,
>	Subashini
>	203-499-3912
>	---------------------------------------------------------
>
>	This e-mail, and any attached file(s), is intended solely for
the use
>	of the individual or entity to whom this e-mail is addressed and
may
>	contain information that is privileged, confidential or exempt
from
>	disclosure. If you are not one of the named recipient(s) or
otherwise
>	have reason to believe that you have received this message in
error,
>	please notify the UI Information Security Manager at
>203-499-3689
>	and delete this message immediately from any computer. Any
>	other use, retention, dissemination, retransmission, printing or
>	copying of this e-mail is strictly prohibited.
>
>
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug

_________________________________________________________________
Get free, personalized online radio with MSN Radio powered by Pandora
http://radio.msn.com/?icid=T002MSN03A07001

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug