Workflow not responding to latest version of the business object

[Mike Nickson]

Perfect, thanks Rick it wasn't recognising the document type for some
reason but you have got me an answer.

Thanks

Mike

On 23 August 2012 15:03, Rick Bakker <rbakker at gmail.com> wrote:

> Mike,
>
> Since you don't have a problem with changing the method, why not try the
> old trick of inserting
> an infinite loop and then connecting to it to run it in debug (as Michael
> suggested).
>
>  * Temporary, for debugging.
> data: lv_tmp(1).
> lv_tmp = 'X'.
> while lv_tmp eq 'X'.
> endwhile.
>
> SM50, find the program (often WF-BATCH) choose debug (Program/Session >
> Program > Debugging)
> and change the value to get out of the loop.
> NB: remember to remove the infinite loop later!
>
> regards
> Rick
>
> On Thu, Aug 23, 2012 at 11:54 PM, <michael.mcley at daimler.com> wrote:
>
>> Mike,
>>
>> 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.
>>
>> So just make sure you are starting a brand new workflow when you are
>> testing a change.
>>
>> 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.
>> **
>>
>> *Michael McLey***
>> MBUSI - IT Parts & Administration
>> Mercedes-Benz US International, Inc.
>> 1 Mercedes Drive
>> Vance, AL 35490
>> PHONE:  (205) 462 - 5239
>> EMAIL:   michael.mcley at daimler.com
>>
>>
>>   *mikenickson at gmail.com*
>> Sent by: sap-wug-bounces at mit.edu
>>
>> 08/23/2012 08:27 AM
>>   Please respond to
>> sap-wug at mit.edu
>>
>>    To
>> SAP-WUG at mit.edu
>> cc
>>   Subject
>> Workflow not responding to latest version of the business object
>>
>>
>>
>>
>> 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.
>>
>> I test the object in the other client and it works fine.
>>
>> 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.
>>
>> 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.
>>
>> Tried OBUF and logging off and on again but still this is mystifying me.
>>
>> The workflow task should be calling the latest version of the object, but
>> this doesn't seem to be happening.
>>
>> Any idea what I have missed ?
>>
>> How come when I test the object it works as I expect, but when the
>> workflow calls the object it doesn't ?
>>
>> Mike_______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>> 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.
>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20120823/9e5afcec/attachment.htm