Workflow Multi Condition Step not working

[Kjetil Kilhavn]

A rare, but possible error is a runtime object which is out of
synchronisation with the development object. I have only experienced it
once (twice?) myself. The one time I can recall now the problem was in
the BOR object's runtime code, and then the problem was visible when
debugging, as the debugger would indicate that an empty line was being
executed, would stop at the "wrong" line of a multi-line statement etc.
The debugger displayed the development object's code, but the runtime
object's code was being executed and was what controlled the line
selection in the debugger.

It would be much harder to pinpoint such an error in the flow itself
since you can't debug it, and the only solution other than re-importing
the transport is re-generation of the runtime object code, in your case
using the "Generate runtime version" menu item in the workflow builder.
-- 
Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP

 

> -----Original Message-----
> From: sap-wug-bounces at mit.edu 
> [mailto:sap-wug-bounces at mit.edu] On Behalf Of Kashif Jabbar
> Sent: Thursday, February 01, 2007 5:16 PM
> To: SAP Workflow Users' Group
> Subject: Re: Workflow Multi Condition Step not working
> 
> Actually after much investigation and hair pulling we found 
> that was not really an issue with the multi condition step. 
> In fact any changes to the workflow were not taking effect. 
> Refreshing the buffer did not help. It was as if the buffer 
> was not getting refreshed. We have the development and 
> testing clients on the same machine. I refreshed the buffer 
> in both clients. I even had the application server restarted.
> Still no luck. Finally we transported the workbench request 
> from the dev client to the test client and it worked.
> 
> This symptom appeared after our system was upgraded and we 
> have a high priority OSS message open with SAP. Hopefully 
> they will figure out what is going on.
> 
> Thank you for replying. If you can shed any light on this it 
> would be great.
> 
> 
> 
> On 2/1/07, Kjetil Kilhavn <KJETILK at statoil.com> wrote:
> > Could you provide a little more information, e.g. how your 
> condition 
> > step is defined? If there is a problem in your definition it is 
> > impossible to spot it without knowing your definition.
> > --
> > Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP
> >
> >
> >
> > > -----Original Message-----
> > > From: sap-wug-bounces at mit.edu
> > > [mailto:sap-wug-bounces at mit.edu] On Behalf Of Kashif Jabbar
> > > Sent: Wednesday, January 31, 2007 5:50 AM
> > > To: sap-wug at mit.edu
> > > Subject: Workflow Multi Condition Step not working
> > >
> > > Hello,
> > >
> > > I am trying to add a new condition to an existing 
> Multiple Condition 
> > > step that is part of a working workflow. However, even 
> when this new 
> > > condition is true the workflow does not go to the new 
> branch rather 
> > > using the OTHER branch as if unable to recognize the 
> condition. The 
> > > pre-existing conditions work without any problems.
> > >
> > > I am baffled by this situation as I have never come 
> across it before.
> > > Can anyone help?
> > >
> > >
> > > Thanks,
> > > Kashif
> > > _______________________________________________
> > > SAP-WUG mailing list
> > > SAP-WUG at mit.edu
> > > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > >
> >
> >
> > -------------------------------------------------------------------
> > The information contained in this message may be 
> CONFIDENTIAL and is 
> > intended for the addressee only. Any unauthorised use, 
> dissemination 
> > of the information or copying of this message is prohibited. If you 
> > are not the addressee, please notify the sender immediately 
> by return 
> > e-mail and delete this message.
> > Thank you.
> >
> > _______________________________________________
> > 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
> 


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.