Hi Mike,<br><br>Good to hear. That trick helped me just the other day when it made me realize I was looking at the wrong object instance.<br><br>Regards<br>Rick<br><br>On Friday, August 24, 2012, Mike Nickson <<a href="mailto:mikenickson@gmail.com">mikenickson@gmail.com</a>> wrote:<br>
> Perfect, thanks Rick it wasn't recognising the document type for some reason but you have got me an answer.<br>> <br>> Thanks<br>> <br>> Mike<br>><br>> On 23 August 2012 15:03, Rick Bakker <<a href="mailto:rbakker@gmail.com">rbakker@gmail.com</a>> wrote:<br>
><br>> Mike,<br>> Since you don't have a problem with changing the method, why not try the old trick of inserting<br>> an infinite loop and then connecting to it to run it in debug (as Michael suggested).<br>
> * Temporary, for debugging.<br>> data: lv_tmp(1).<br>> lv_tmp = 'X'.<br>> while lv_tmp eq 'X'.<br>> endwhile.<br>> SM50, find the program (often WF-BATCH) choose debug (Program/Session > Program > Debugging) <br>
> and change the value to get out of the loop.<br>> NB: remember to remove the infinite loop later!<br>> regards<br>> Rick<br>> On Thu, Aug 23, 2012 at 11:54 PM, <<a href="mailto:michael.mcley@daimler.com">michael.mcley@daimler.com</a>> wrote:<br>
><br>> Mike,<br>><br>> 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. <br>
><br>> So just make sure you are starting a brand new workflow when you are testing a change.<br>><br>> 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>
><br>> Michael McLey<br>> MBUSI - IT Parts & Administration<br>> Mercedes-Benz US International, Inc.<br>> 1 Mercedes Drive<br>> Vance, AL 35490<br>> PHONE: (205) 462 - 5239<br>> EMAIL: <a href="mailto:michael.mcley@daimler.com">michael.mcley@daimler.com</a> <br>
><br>><br>> <a href="mailto:mikenickson@gmail.com">mikenickson@gmail.com</a><br>> Sent by: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><br>><br>> 08/23/2012 08:27 AM<br>><br>> Please respond to<br>
> <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>> To<br>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>> cc<br>> Subject<br>> Workflow not responding to latest version of the business object<br>
><br>><br>><br>><br>> 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 o