Workflow not responding to latest version of the business object

[Mike Nickson]

Jimmy

No I am creating a new purchase order that is triggering a new workflow
instance.

Mike

On 23 August 2012 14:48, Jimmy Sun <jjsun02 at gmail.com> wrote:

> Mike,
> are you testing with an old workitem? Start a new workitem and check it
> again?
>
> Jimmy
>
>
> On Thu, Aug 23, 2012 at 9:41 AM, Mike Nickson <mikenickson at gmail.com>wrote:
>
>> Hi Rick
>>
>> Yes ZBUS2012 delegated as sub object of BUS2012, adn the workflow is
>> using BUS2012.
>>
>> I am loath to change the workflow as we are in the middle of QA testing,
>> so trying to contain all changes via the object.
>>
>> I bet this will all work tomorrow, but I am short of time here.
>> Mike
>>  On 23 August 2012 14:33, Rick Bakker <rbakker at gmail.com> wrote:
>>
>>> Hello,
>>>
>>> So you did SWU_OBUF and you activated the object and, I assume, a new
>>> workflow instance was started.
>>>
>>> The only thing I can think of is that you're not using the object
>>> intended. Is ZBUS2012 delegated or is it a copy?
>>> Does BUS2012 have a method of the same name?
>>>
>>> regards
>>> Rick Bakker / hanabi technology
>>>
>>> On Thu, Aug 23, 2012 at 11:24 PM, Mike Nickson <mikenickson at gmail.com>
>>> wrote:
>>> > 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
>>> >
>>> _______________________________________________
>>> 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
>>
>>
>
>
> --
> Jimmy
>
>
>
> _______________________________________________
> 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/951f93cf/attachment.htm