<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>"Grouping" workflow & sub-flow releases</title>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:HouschkaBold;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Andy, <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Versioning is good as long as you are only making compatible (version-dependent)
changes. This holds true for a single workflow and also applies to your
scenario. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>To me it sounds like an incompatible change which would at the
very least require a new subflow. I suppose you could build in some logic to
detect what version it’s being called from but that’s a bit too much of a
sledgehammer approach for my liking. Besides, it takes a couple of minutes to create
a copy and plug that into your main flow. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Cheers, <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Mike<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Catherall, Andy M<br>
<b>Sent:</b> 20 May 2008 11:53<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> "Grouping" workflow & sub-flow releases<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Hi all</span>
<o:p></o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I'm curious
to see if any cunning work-arounds have been developed for the following
example scenario: </span><o:p></o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>* I have a
workflow with a sub-flow. </span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>* This subflow
is called some-way through the main-flow, and hence there can be several
instances of the main-flow active that have not yet got so far as to call the
sub-flow.</span><o:p></o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>* I would
like to change the design of both the main-flow & sub-flow in some way,
such that the new sub-flow design is reliant upon the change in the main-flow
design (eg A step in the main-flow does something, a step in the sub-flow now
expects that that something has been done).</span><o:p></o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>* If I
release these two new workflows into production, there is the following risk:</span>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>A workflow
instance which began when the old design was active now reaches the subflow,
but calls the *new* version. As described above, the subflow expects that the
mainflow has completed something, but as the old design of the mainflow was
being used, this is not correct. Errors will probably now occur.</span><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>What would
be great is if it were possible to associate subflow versions with mainflow
versions so that we could effectively version up the package, rather than just
the individual workflow templates. However, I'm not aware of this being available
on any version.</span><o:p></o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Any ideas? </span><o:p></o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Cheers</span>
<br>
<span style='font-size:10.0pt;font-family:"HouschkaBold","serif";color:blue'>Andy
Catherall</span> <br>
<span style='font-size:10.0pt;font-family:"HouschkaBold","serif";color:blue'>Technical
Analyst - SAP Workflow, IXOS & DMS</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><img
id="_x0000_i1025" src="cid:image001.png@01C8BA77.7E59AD60"
alt="Picture (Metafile)"></span><br>
<span style='font-size:7.5pt;font-family:"HouschkaBold","serif"'>Int: 751 0556</span>
<br>
<span style='font-size:7.5pt;font-family:"HouschkaBold","serif"'>Ext: +44
(0)121 415 0556</span> <br>
<span style='font-size:7.5pt;font-family:"HouschkaBold","serif"'>Mobile: +44
(0)7813 025481</span> <o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal align=center style='text-align:center;line-height:150%'><b><span
style='font-size:10.0pt;line-height:150%;font-family:"Verdana","sans-serif";
color:maroon'>Cadbury Cocoa Partnership – a historic alliance to secure the
future of cocoa farming. Visit</span></b><b><span style='font-size:10.0pt;
line-height:150%;font-family:"Verdana","sans-serif";color:black'> </span></b><b><u><span
style='font-size:10.0pt;line-height:150%;font-family:"Verdana","sans-serif";
color:blue'><a href="http://www.cadbury.com/">www.cadbury.com</a></span></u></b><b><span
style='font-size:10.0pt;line-height:150%;font-family:"Verdana","sans-serif";
color:black'> </span></b><b><span style='font-size:10.0pt;line-height:150%;
font-family:"Verdana","sans-serif";color:maroon'>to learn more</span><span
style='color:maroon'><o:p></o:p></span></b></p>
<p class=MsoNormal align=center style='text-align:center'><b><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:green'> </span><span
style='color:maroon'><o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:green'>Please support our Purple Goes Green commitments and consider the
environment before you print this email</span><span style='color:maroon'><o:p></o:p></span></b></p>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=MsoNormal>-----------------------------------------<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:8.0pt;margin-right:0cm;margin-bottom:
8.0pt;margin-left:0cm'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>This
email (including any attachment) is confidential and may contain privileged
information. If you are not the intended recipient or receive it in error, you
may not use, distribute, disclose or copy any of the information contained
within it and it may be unlawful to do so. If you are not the intended
recipient please notify us immediately by returning this email to us at </span><a
href="mailto:mailerror@csplc.com" title="mailto:mailerror@csplc.com"><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><mailto:mailerror@csplc.com></span></a><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> and destroy all
copies.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:8.0pt;margin-right:0cm;margin-bottom:
8.0pt;margin-left:0cm'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Any
views expressed by individuals within this email do not necessarily reflect the
views of Cadbury Holdings Ltd or any of its subsidiaries or affiliates. This
email does not constitute a binding offer, acceptance, amendment, waiver or
other agreement, unless such intention is clearly stated in the body of the
email. Whilst we have taken reasonable steps to ensure that this email and
attachments are free from viruses, recipients are advised to subject this email
to their own virus checking, in keeping with good computing practice. Please
note that email received by Cadbury Holdings Ltd or its subsidiaries or affiliates
may be monitored in accordance with applicable law. </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:8.0pt;margin-right:0cm;margin-bottom:
8.0pt;margin-left:0cm'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Cadbury
Holdings Ltd registered in England and Wales, no. 52457. <br>
Registered address: 25 Berkeley Square, London, W1J 6HB, United Kingdom<br>
Telephone: +44 (0) 20 7409 1313 Fax: +44 (0) 20 7830 5200</span><o:p></o:p></p>
<p class=MsoNormal><span lang=EN-US>-----------------------------------------</span><o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>