<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type><TITLE>Adding Exceptions to Object =
Methods</TITLE>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY>
<DIV><SPAN class=3D230155209-19012000><FONT color=3D#0000ff face=3DArial =
size=3D2>I=20
wouldn't do anything if you don't want to change the workflow =
definition. If you=20
add the exceptions in the method definition, nothing will happen - apart =
from=20
error messages that might change because you're now creating a different =
error=20
than before, ie. exceptions not modelled in definition instead of =
exceptions not=20
defined in method. However, the next time you enter the activity details =
in your=20
workflow definition, you will see the exception in the appropriate tab. =
If you=20
put any text in the event field behind the newly defined exceptions, the =
graphical overview will pick them up and you can model =
them.</FONT></SPAN></DIV>
<DIV><SPAN class=3D230155209-19012000><FONT color=3D#0000ff face=3DArial =
size=3D2></FONT></SPAN><SPAN class=3D230155209-19012000><FONT =
color=3D#0000ff=20
face=3DArial size=3D2>Because you wouldn't actually enhance anything in =
my view, I'd=20
just leave it until you really have to change the workflow, and then do =
it in=20
one swoop..</FONT></SPAN></DIV>
<DIV><SPAN class=3D230155209-19012000><FONT color=3D#0000ff face=3DArial =
size=3D2></FONT></SPAN><SPAN class=3D230155209-19012000><FONT =
color=3D#0000ff=20
face=3DArial size=3D2>Stephan</FONT></SPAN></DIV>
<DIV><SPAN class=3D230155209-19012000><FONT color=3D#0000ff face=3DArial =
size=3D2></FONT></SPAN><FONT face=3D"Times New Roman" size=3D2><SPAN=20
class=3D230155209-19012000><FONT color=3D#0000ff face=3DArial=20
size=3D2> </FONT></SPAN></FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2><SPAN =
class=3D230155209-19012000><FONT=20
color=3D#0000ff face=3DArial size=3D2></FONT></SPAN></FONT> </DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2><SPAN =
class=3D230155209-19012000><FONT=20
color=3D#0000ff face=3DArial size=3D2> </FONT></SPAN>-----Original=20
Message-----<BR><B>From:</B> SAP Workflow=20
[mailto:Owner-SAP-WUG@MITVMA.MIT.EDU]<B>On Behalf Of</B> Schroeter,=20
Brad<BR><B>Sent:</B> 18 January 2000 21:05<BR><B>To:</B>=20
SAP-WUG@MITVMA.MIT.EDU<BR><B>Subject:</B> Adding Exceptions to Object=20
Methods<BR><BR></FONT></DIV>
<BLOCKQUOTE>
<P><FONT face=3DArial size=3D2>I've found some =
"exit_return"=20
statements in our methods which don't have a corresponding object =
method=20
exception. My plan is to go add the appropriate exceptions to =
the=20
object methods. My question is this: will doing this require =
any=20
changes to the actual workflows (we're in production)? From I =
can see,=20
it won't. However I'd like to make sure. I've attached =
the=20
sections from OSS note 125400 (Modifying a Productive Workflow) =
which=20
pertain to Business Objects. Thanks...</FONT></P>
<P><FONT face=3DArial size=3D2>"Modifying a Business Object =
Method</FONT>=20
<BR><FONT face=3DArial size=3D2>Usually an incompatible =
change.</FONT> <BR><FONT=20
face=3DArial size=3D2>When in doubt, create a new method, =
encapsulate it in a=20
new task which</FONT> <BR><FONT face=3DArial size=3D2>is called from =
a new=20
workflow version.</FONT> <BR><FONT face=3DArial size=3D2>If the =
method's=20
implementation has changed (ABAP code), but neither the</FONT> =
<BR><FONT=20
face=3DArial size=3D2>method's interface nor the properties =
have changed,=20
the workflow and</FONT> <BR><FONT face=3DArial size=3D2>task do not =
need to be=20
changed.</FONT> </P>
<P><FONT face=3DArial size=3D2>Modifying a Business Object =
Attribute</FONT>=20
<BR><FONT face=3DArial size=3D2>Sometimes this is an incompatible =
change. Read=20
on.</FONT> <BR><FONT face=3DArial size=3D2>Changing the algorithm =
behind an=20
attribute will not affect the workflow</FONT> <BR><FONT face=3DArial =
size=3D2>definition.</FONT> <BR><FONT face=3DArial size=3D2>Changing =
the=20
attribute's data repository reference could affect the task</FONT> =
<BR><FONT=20
face=3DArial size=3D2>container and consequently the workflow =
container and=20
binding. Create a</FONT> <BR><FONT face=3DArial size=3D2>new =
workflow.</FONT>=20
<BR><FONT face=3DArial size=3D2>Changing the multi-line flag of the =
attribute=20
will have consequences for</FONT> <BR><FONT face=3DArial =
size=3D2>the workflow=20
and its container, so you need to create a new =
workflow."</FONT>=20
</P><BR>
<P><FONT face=3DArial size=3D2>Brad Schroeter</FONT> <BR><FONT =
face=3DArial=20
size=3D2>E-mail: BSchroeter@ti.com</FONT> =
</P><BR></BLOCKQUOTE></BODY></HTML>