Multiple Conditions Step

[Jeffrey A. Rappaport]

Casey,
 
   This could also be a Buffer issue. After adding the new condition,
do you Activate, then back all the way out & run Tranx: SWU_OBUF? Or
have you waited till the next day to run a test to see if it works?
If it does, then it's a Buffer issue, which can many times be a Pain!
 
Jeffrey A. Rappaport
Business Workflow, LLC
Voice:(732)355-0123
Fax:  (509)757-4144
Email:Jeff at Business-Workflow.com
Web:  www.Business-Workflow.com
 
 
Quoting Richard Marut <rvmarut at earthlink.net>:
 
> Casey,
>
> Whenever I need to add another outcome to multiple condition step,
> I would
> recreate the step with the same conditions plus the new one just
> before the
> existing condition step. I then copied the tasks from the original
> step to
> their appropriate paths and then deleted the old condition.
>
> I've experienced the same problem as you and this was the only
> solution I
> could come up with. It's a little extra work but it solves the
> problem.
>
> Richard...
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf
> Of Smith,
> Cassaundra
> Sent: Monday, May 24, 2004 9:54 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Multiple Conditions Step
>
> All
>
> We are on 4.6C. I had a previous workflow with a multiple
> conditions step.
> The
> workflow started off with only 3 conditions and an Others branch.
> Now I
> have
> added a fourth condition.  But for some reason, the workflow is not
> recognizing
> this fourth condition and treats it as 'others' and ends the
> workflow.  I
> check
> the workflow log object variable and it indeed is an N, this new
> condition
> expression.  I checked the workflow and N is listed as a possible
> condition.
> Have any of you ever experienced this problem.
>
> Please Advise,
>
> Casey
>