WF Start Conditions

[Nobles, Diane]

Is there a limit to the number of conditions it can evaluate, i.e.,
variables versus strings??
 
Diane H. Nobles
SAP Proj. Analyst, PM, WF
(757) 380-7250
 
 
-----Original Message-----
From: Cooper, John M [mailto:jcooper at kcc.com]=20
Sent: Tuesday, October 08, 2002 12:56 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: WF Start Conditions
 
 
It is the same idea as in programming for math operations, and it is =
called
Boolean logic or sometimes Boolean algebra.  If you do a search on the =
web
for either term you will find quite a few written references.
 
In the start condition you use the parentheses to group multiple =
logical
statements into one, so that it can be evaluated and assigned a value =
of
true or false in the correct order.  In the start condition you are =
using,
the parentheses group the check for notification type into one logical
statement, so that if one of the "or" conditions is true then the =
entire
statement within the parentheses is true (i.e. if the notif type is V1, =
V2,
V3, or V4, the statement evaluates to true.)  Once that is done, the =
rest of
the condition is evaluated, so that if the notif type logic is true AND =
the
task number is 0001, then the condition is true and the workflow will =
start.
 
-----Original Message-----
From: Nobles, Diane [mailto:nobles_dh at naptheon.com]=20
Sent: Tuesday, October 08, 2002 10:57 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: WF Start Conditions
 
 
Thanks John.  Works like a charm.  I knew the trick had to be the
parenthesis.  Are there any guidelines or rules written anywhere, i.e.,
mathematical uses of parenthesis etc., for start conditions, or is it
basically just like math programming rules?=20
 
 
Diane H. Nobles
SAP Proj. Analyst, PM, WF
(757) 380-7250
 
 
-----Original Message-----
From: Cooper, John M [mailto:jcooper at kcc.com]=20
Sent: Tuesday, October 08, 2002 10:14 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: WF Start Conditions
 
 
Have you tried grouping all the "or" conditions together so that the =
system
evaluates the condition correctly? =20
 
                (Tasks.Notif Type        =3D 'V1'         =09
  or            Tasks.Notif Type        =3D 'V2'         =09
  or            Tasks.Notif Type        =3D 'V3'         =09
  or            Tasks.Notif Type        =3D 'V4' )        =09
  and           Tasks.Task Number       =3D 0001
 
 
-----Original Message-----
From: Nobles, Diane [mailto:nobles_dh at naptheon.com]=20
Sent: Tuesday, October 08, 2002 8:57 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: WF Start Conditions
 
 
Good morning all.  I am working with workflow start conditions and I =
need to
trigger a workflow for a task based on number.  The Event is Task =
Released,
i.e., task with status Released.  My problem is that Task number one =
will
remain in Released status during the creation and processing of other =
tasks
on the same object and each time the other tasks are released the =
system
activates the workflow for Task #1 also.  Need to be able to create a =
false
condition for this task #1, when task equal to or greater than 2 =
exists.  Is
this possible??  IF not what can I do to work around.  See two =
conditions
below that I have already tried and failed.=20
=20
=20
=20
=09
 
 
 
 
 
=20
 
 
 
                Tasks.Notif Type        =3D 'V1'         =09
  or            Tasks.Notif Type        =3D 'V2'         =09
  or            Tasks.Notif Type        =3D 'V3'         =09
  or            Tasks.Notif Type        =3D 'V4'         =09
  and           Tasks.Task Number       =3D 0001         =09
  and      not           Tasks.Task Number      =99 0002=09
=20
=20
=09
 
 
 
 
 
=20
 
 
 
=20
 
                Tasks.Notif Type        =3D 'V1'         =09
  or            Tasks.Notif Type        =3D 'V2'         =09
  or            Tasks.Notif Type        =3D 'V3'         =09
  or            Tasks.Notif Type        =3D 'V4'         =09
  and      not           Tasks.Task Number      =99 0002=09
=20
=20
=20
Diane H. Nobles
SAP Proj. Analyst, PM, WF
(757) 380-7250
=20
 
------------------------------------------------------------------------=
----
--
This e-mail is intended for the use of the addressee(s) only and may =
contain
privileged, confidential, or proprietary information that is exempt =
from
disclosure under law.  If you have received this message in error, =
please
inform us promptly by reply e-mail, then delete the e-mail and destroy =
any
printed copy.   Thank you.
 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=3D=3D
 
------------------------------------------------------------------------=
----
--
This e-mail is intended for the use of the addressee(s) only and may =
contain
privileged, confidential, or proprietary information that is exempt =
from
disclosure under law.  If you have received this message in error, =
please
inform us promptly by reply e-mail, then delete the e-mail and destroy =
any
printed copy.   Thank you.
 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=3D=3D