Condition step not working in Workflow

Wed Feb 27 18:58:23 EST 2008

Hi Sue:
Just another option:
I hope you might have created object instance step in
your workflow and setup proper bindings, if not please
do so; looks like the workflow is not recognizing the
data you are passing. I hope this helps you.
Regards,
Aziz.
--- Shai Eyal <shai.eyal at yahoo.com> wrote:

> Sue,
>  
> I recalled another weird situation I had. In case
> you development client is different than the one you
> carry the tests (but both on same server!!) run SCC1
> to copy transport to test client. I know it should
> not be relevant for workbench requests but in
> certain BASIS level (which I can't remember) record
> in table that was suppose to be customization was
> recorded on workbench request.
>  
> In addition, pay attention your container elements
> do not have initial values !!
>  
> Please try & notify.
>  
> 
>  
> Regards,
> Shai Eyal
> SAP Logistics senior consultant
> SAP Workflow specialist
> Mobile: 972-52-5816633
> 
> 
> 
> ----- Original Message ----
> From: "sap-wug-request at mit.edu"
> <sap-wug-request at mit.edu>
> To: sap-wug at mit.edu
> Sent: Wednesday, February 27, 2008 21:45:27
> Subject: SAP-WUG Digest, Vol 39, Issue 72
> 
> Send SAP-WUG mailing list submissions to
>     sap-wug at mit.edu
> 
> To subscribe or unsubscribe via the World Wide Web,
> visit
>     http://mailman.mit.edu/mailman/listinfo/sap-wug
> or, via email, send a message with subject or body
> 'help' to
>     sap-wug-request at mit.edu
> 
> You can reach the person managing the list at
>     sap-wug-owner at mit.edu
> 
> When replying, please edit your Subject line so it
> is more specific
> than "Re: Contents of SAP-WUG digest..."
> 
> 
> Today's Topics:
> 
>   1. RE: Condition step not working in Workflow (Sue
> Doughty)
>   2. RE: SAP-WUG Digest, Vol 39, Issue 71 (yogesh
> patil)
> 
> 
>
----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 27 Feb 2008 13:20:16 -0500
> From: "Sue Doughty" <Sue.Doughty at odfl.com>
> Subject: RE: Condition step not working in Workflow
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
>    
>
<082C942F46528B44B5463D3C2A1FF0F40E5BACF3 at corp-m-exch2.corp.odfl.com>
> Content-Type: text/plain;    charset="us-ascii"
> 
> Hi Mike,
> 
> I changed the data type to SY-INPUT and still get
> the same results.
> 
> Thank you for the suggestion though.  I'm willing to
> try anything.  I
> hope that it is not something so simple that I'll
> feel really stupid
> when I find it.  :-)
> 
> Regards,
> Sue T. Doughty
> SAP Workflow Specialist
> Old Dominion Freight Line, Inc.
> 500 Old Dominion Way
> Thomasville, NC 27360
> Phone:  (336) 822-5189
> Toll Free (800 ) 432-6335, ext. 5189
> Email:  sue.doughty at odfl.com
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Pokraka
> Sent: Wednesday, February 27, 2008 12:13 PM
> To: SAP Workflow Users' Group
> Subject: RE: Condition step not working in Workflow
> 
> Hmm, not too sure then. I thought I'd mention as it
> would be worth
> checking. Also make sure your data type is valid for
> the values. Try
> changing it to SY-INPUT just to make sure.
> 
> On Wed, February 27, 2008 4:11 pm, Sue Doughty
> wrote:
> > Hi Mike,
> >
> > Thanks for your reply.
> >
> > I am not using a result parameter even though I
> tried that when it did
> > not work the way I had it at first.  Neither way
> works.  I can see in
> > the workflow log that my export parameter
> (ImageFound) is being
> > populated with the correct 'T' or 'F' value, but
> the Results
> processing
> > step is not being executed with an F value - it
> only executes when the
> > export parameter contains a 'T' value.
> >
> > I can't use a virtual attribute because the input
> parameters to the
> > method change with each call to the method (i.e.,
> doctype and
> > imagedate).
> >
> > Regards,
> > Sue T. Doughty
> > SAP Workflow Specialist
> > Old Dominion Freight Line, Inc.
> > 500 Old Dominion Way
> > Thomasville, NC 27360
> > Phone:  (336) 822-5189
> > Toll Free (800 ) 432-6335, ext. 5189
> > Email:  sue.doughty at odfl.com
> > -----Original Message-----
> > From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu] On
> Behalf
> > Of Mike Pokraka
> > Sent: Wednesday, February 27, 2008 10:44 AM
> > To: SAP Workflow Users' Group
> > Subject: Re: Condition step not working in
> Workflow
> >
> > Hi Sue,
> > Are you using a standard return parameter or a
> result parameter?
> > ("Result
> > parameter" checkbox on your method properties).
> > Result parameters behave differently, T/F must be
> defined within the
> > data
> > dictionary and become separate outcomes of the
> method.
> > Also, perhaps a virtual attribute might be easier
> if this is all that
> > the
> > method does...
> >
> > Cheers,
> > Mike
> >
> > On Tue, February 26, 2008 5:06 pm, Sue Doughty
> wrote:
> >> We are on 4.7, ECC 6.0
> >>
> >>
> >>
> >> I have a sub-workflow that executes a loop until
> a result flag is set
> > to
> >> T.  It executes a method that reads a table with
> some information.
> If
> >> the record is found, the result is set to T, if
> not it is set to F
> and
> >> the result container is set in the method.  The
> next step is a
> > condition
> >> to check the result.  If T, the loop and
> sub-workflow are completed,
> > if
> >> F, it waits and tries again after five minutes.
> >>
> >>
> >>
> >> My problem:  If the method executes and the
> result is T, the workflow
> >> works as designed.  If the method returns a
> result of F, the workflow
> >> stops at that step and does not move to the
> condition step to check
> > the
> >> result.
> 
=== message truncated ===>
_______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>