<br><font size=2 face="sans-serif">Thankyou somuch for replies, It was
good, </font>
<br>
<br><font size=2 face="sans-serif">I backed out my change(Made a copy of
Flow template with changes i had made) & First moved another developer's
changes to PRD. then i put back my changes & transported mine to PRD.</font>
<br>
<br><font size=2 face="sans-serif">Thanks,<br>
Subashini<br>
203-499-3912</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Munday,Sherie J."
<MUNDAYSJ@airproducts.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">12/21/2006 09:24 AM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"SAP Workflow Users' Group"
<sap-wug@mit.edu></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: How to get ack to Old version of
workflow template</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Mike,<br>
Thanks for the clarification!! <br>
We are a small workflow team, so we keep things simple by keeping just<br>
'000' in dev and communicating thoroughly about our changes, but it is<br>
enlightening to see the possibilities for others with more complex<br>
teams.<br>
Cheers & Happy Holidays,<br>
Sherie<br>
<br>
Sherie Munday<br>
Workflow Developer & Analyst<br>
Air Products & Chemicals, Inc. <br>
<br>
-----Original Message-----<br>
From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<br>
Of Mike Gambier<br>
Sent: Thursday, December 21, 2006 5:04 AM<br>
To: sap-wug@mit.edu<br>
Subject: RE: How to get ack to Old version of workflow template<br>
<br>
Subashi, Sherie,<br>
<br>
A word of caution on WF Versions: as far as I know, although I'm<br>
prepared to be corrected on this, the container is NOT version<br>
controlled so be very very careful about mixing changes. It's very easy<br>
to assume that version Management in Workflow is the same as it is in<br>
ABAP and rolling back changes or jumping between versions is a piece of<br>
cake, unfortunately it is not. <br>
It's about 90% effective really.<br>
<br>
If you have deleted any container elements or changed the nature of<br>
existing elements I recommend you double-check the production version<br>
closely and make sure you are 100% confident the changes will not affect<br>
any live instances because they will be immediately affected by your<br>
changes.<br>
<br>
Adding new elements should be fine provided those elements are entirely<br>
new and not used by any steps in previous versions of the definition and<br>
of course they must syntax check (new elements based on data types or<br>
objects left behind in development will cause activation errors in your<br>
definition).<br>
<br>
You can create 'new' versions of WF definitions in development (so you<br>
don't actually have to be working on the same version all the time, or<br>
indeed continuously update version '0000'). I have found this to be<br>
particularly useful if I am adding or removing entire blocks and<br>
therefore significantly changing the definition as it cleary shows to<br>
someone else how the definition has evolved. But be sure to activate<br>
your new version before you start, otherwise you may fool yourself into<br>
thinking you are then changing your new version when you may not be at<br>
all.<br>
<br>
Sometimes as an extra precaution, should I forsee the need to manually<br>
undo things, I print off the definition from SWDD as a hard copy (how<br>
old school?), so at least I have an idea of the sequence of things<br>
before I start to change them.<br>
<br>
For most other defintiion changes if somebody has changed the same<br>
definition as you but their Transport was released in your development<br>
environment BEFORE you managed to make any change, then you should be<br>
covered by the Transport mechanism at least, which will have taken a<br>
snapshot of the definition table entries as they were. But, if you<br>
managed to change the definition and their Transport was released<br>
AFTERWARDS (perhaps you added your changes to their Transport) you'll<br>
find that your changes will have been dragged along, whether you wanted<br>
them to or not.<br>
<br>
We have adopted the practice of 'protecting' our Transports in<br>
development to avoid other developers tacking on their changes to<br>
objects unintentionally like this. You may want to do the same.<br>
<br>
MGT<br>
<br>
>From: "Munday,Sherie J." <MUNDAYSJ@airproducts.com><br>
>Reply-To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
>To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
>Subject: RE: How to get ack to Old version of workflow template<br>
>Date: Wed, 20 Dec 2006 13:54:15 -0500<br>
><br>
>Subashini,<br>
>I have a little different spin on your question...<br>
><br>
>If all of the other person's changes were made prior to yours and his
<br>
>transport is separate from yours, then certainly his can move without
<br>
>yours. When your changes/transport moves at a later date, it
will <br>
>create the next version in that next system.<br>
><br>
>However, if you have both been making changes, saving, activating and
<br>
>making transports to the same template in dev, then they are mixed
<br>
>together in the same version. In development there is only one
version<br>
<br>
>... 000 and presumably you have both been making changes to that <br>
>version. If this is the case, and his are ready to move to production,
<br>
>you will need to back out/remove your changes or he will have to wait
<br>
>until yours are ready for production.<br>
>Best Wishes,<br>
>Sherie<br>
><br>
>Sherie Munday<br>
>Workflow Developer/Analyst<br>
>Air Products & Chemicals, Inc.<br>
><br>
><br>
>-----Original Message-----<br>
>From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On <br>
>Behalf Of Shrestha, Bijay<br>
>Sent: Tuesday, December 19, 2006 8:50 PM<br>
>To: SAP Workflow Users' Group; sap-wug@mit.edu<br>
>Subject: RE: How to get ack to Old version of workflow template<br>
><br>
>Hi Subashini,<br>
><br>
>First you should generate and release the correct and ready version
to <br>
>Prod. Then in Dev. environment you can retrieve the old version by
<br>
>clicking on other version in Workflow Builder. Then you can keep making<br>
<br>
>changes.<br>
><br>
>Bijay Shrestha<br>
>Sr. Consultant<br>
>Pragmatek Consulting Gr.<br>
><br>
>
-----Original Message-----<br>
>
From: sap-wug-bounces@mit.edu on behalf of <br>
>Subashini.Bhoopathiraj@uinet.com<br>
>
Sent: Tue 12/19/2006 6:59 PM<br>
>
To: sap-wug@mit.edu<br>
>
Cc:<br>
>
Subject: How to get ack to Old version of workflow template<br>
><br>
><br>
><br>
>
Hi all,<br>
><br>
>
I have made some changes to the workflow template, another<br>
person <br>
>also made the changes to the same workflow template, but my changes
not<br>
<br>
>yet tested, so it shouldn't move into production.<br>
><br>
>
But other person's changes should move in Production with out<br>
my <br>
>changes . I thought of activating Old version & other person can
do the<br>
<br>
>change & transport to PRD. after that i can retrive my version
& <br>
>transport to the production. How can i do this??<br>
><br>
>
Thanks,<br>
>
Subashini<br>
>
203-499-3912<br>
>
---------------------------------------------------------<br>
><br>
>
This e-mail, and any attached file(s), is intended solely for<br>
the use<br>
>
of the individual or entity to whom this e-mail is addressed and<br>
may<br>
>
contain information that is privileged, confidential or exempt<br>
from<br>
>
disclosure. If you are not one of the named recipient(s) or<br>
otherwise<br>
>
have reason to believe that you have received this message in<br>
error,<br>
>
please notify the UI Information Security Manager at<br>
>203-499-3689<br>
>
and delete this message immediately from any computer. Any<br>
>
other use, retention, dissemination, retransmission, printing or<br>
>
copying of this e-mail is strictly prohibited.<br>
><br>
><br>
><br>
>_______________________________________________<br>
>SAP-WUG mailing list<br>
>SAP-WUG@mit.edu<br>
>http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
><br>
>_______________________________________________<br>
>SAP-WUG mailing list<br>
>SAP-WUG@mit.edu<br>
>http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
<br>
_________________________________________________________________<br>
Get free, personalized online radio with MSN Radio powered by Pandora<br>
http://radio.msn.com/?icid=T002MSN03A07001<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
</tt></font>
<br>
<pre>---------------------------------------------------------
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.