<font size=2 face="sans-serif">Mike,</font><br><br><font size=2 face="sans-serif">The only advice I can offer here (and
the WUG can correct me if I'm wrong) is that workflow instances seem to
maintain a lot of contextual information relating to the status of all
the objects (workflows, tasks, methods, etc...) that were active at the
time the workflow was started. Meaning in a lot of cases new changes
will not be evident on old workflows. </font><br><br><font size=2 face="sans-serif">So just make sure you are starting a
brand new workflow when you are testing a change.</font><br><br><font size=2 face="sans-serif">If this isn't relevant, I seem to remember
there is a way to enter the debugger when you are testing a workflow. But
you have to change the task to foreground and click a couple of buttons
in SWUS (maybe in the options dialog) after setting a breakpoint in the
code. Maybe someone else knows how to do this.<br></font><font size=4 color=#808000><b> </b></font><p><font size=4 color=#808000><b>Michael McLey</b></font><font size=3 color=#808000><b></b><br>MBUSI - IT Parts & Administration </font><font size=2 color=#808000><br>Mercedes-Benz US International, Inc.</font><font size=3 color=#808000></font><font size=2 color=#808000><br>1 Mercedes Drive</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>Vance, AL 35490</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>PHONE: (205) 462 - 5239</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>EMAIL: michael.mcley@daimler.com</font><font size=3 color=#808000>
</font><br><br><br><table width=100%><tr valign=top><td width=40%><font size=1 face="sans-serif"><b>mikenickson@gmail.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">08/23/2012 08:27 AM</font><table border><tr valign=top><td bgcolor=white><div align=center><font size=1 face="sans-serif">Please respond to<br>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-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">Workflow not responding to latest version
of the business object</font></table><br><table><tr valign=top><td><td></table><br></table><br><br><br><font size=3>I have amended a method on ZBUS2012 to exit on a certain
document type (ZA) rather than perform the rest of the method code, saved
and generated the object in the development client.<br> <br>I test the object in the other client and it works fine.<br> <br>The workflow though seems to be hanging on to the old version of the object
code, and the results I am getting in the task container that calls the
method seems to be ignoring the new version of the code and it is not just
exiting and returning as I expect.</font><br><font size=3> </font><br><font size=3>I have even added a random error message to one
of the method output parameters to see if it is using the new version of
the object, to no avail.<br> <br>Tried OBUF and logging off and on again but still this is mystifying me.<br> <br>The workflow task should be calling the latest version of the object, but
this doesn't seem to be happening.<br> <br>Any idea what I have missed ?<br> <br>How come when I test the object it works as I expect, but when the workflow
calls the object it doesn't ?</font><br><font size=3> </font><br><font size=3>Mike</font><tt><font size=2>_______________________________________________<br>SAP-WUG mailing list<br>SAP-WUG@mit.edu<br></font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br></font></tt><br><font face="sans-serif"><font face="sans-serif, Arial, Helvetica" size="-1" color="#808080"><br>If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation.
<br></br>
</font></font>