I verified that the filter in question is the culprit, and there
currently is no else action on it.  I think Axton is probably right
though.  I'll pop a message and make sure the values are actually what I
think they are when the workflow fires.

I think the problem might be between the keyboard and the chair.  I
can't duplicate the problem for the life of me now.

Thanks for your help though, everyone.

Michael A. McManus, SrA, USAF
Remedy Developer
HQ 754 ELSG/DOOH
DSN: 596-6478/Comm: 334-416-6478
 
 

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96
CS/SCCE
Sent: Wednesday, April 25, 2007 12:21 PM
To: [email protected]
Subject: Re: Boolean Logic

Michael:

What Axton said is probably your problem:

Just because you see field x with value y does not mean that the fields
have that value when the workflow fires.

The qualification is probably being evaluated BEFORE the field is being
set with the value you're validating with your eyes.

Also, make sure there isn't a duplicate AL or filter in the mix.  And
make sure there isn't an ELSE action in the mix, too.  It's easy to sit
and bang your head on the wall over a qualification when the message is
actually being fired by some other piece of workflow.

Norm

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Axton
Sent: Wednesday, April 25, 2007 11:59 AM
To: [email protected]
Subject: Re: Boolean Logic

Your boolean looks like this:

A AND B

Where
A=(( 'Dialog_Prev_Status' =  "Closed" ) OR ( 'Dialog_Prev_Status' =
"Helpdesk Working" ) OR ( 'Dialog_Prev_Status' =  "Pending Vendor" ))
B=(($GROUPS$ LIKE  "%System POC%" ) OR ($GROUPS$ LIKE  "%Reshipment%"
) OR ($GROUPS$ LIKE  "%Quality Assurance%" ))

So long as one of the conditions of A and one of the conditions of B
are true, it will fire.

You didn't state what the object type or the trigger's were, but I
would suggest you add a message action to this workflow object, and in
the message return $GROUPS$ and 'Dialog_Prev_Status' so you know the
values the workflow is evaluating it's run if against.

Just because you see field x with value y does not mean that the
fields have that value when the workflow fires.

Axton Grams

On 4/25/07, McManus Michael A SrA HQ 754 ELSG/DOO
<[EMAIL PROTECTED]> wrote:
> **
>
>
>
> Version 5.1.2
>
> SQL 2K
>
>
>
> I'm having problems with a run if condition that isn't allowing our
System
> POC's to send emails.  Here's the condition.
>
>
>
> (( 'Dialog_Prev_Status' =  "Closed" ) OR ( 'Dialog_Prev_Status' =
"Helpdesk
> Working" ) OR ( 'Dialog_Prev_Status' =  "Pending Vendor" )) AND
(($GROUPS$
> LIKE  "%System POC%" ) OR ($GROUPS$ LIKE  "%Reshipment%" ) OR
($GROUPS$ LIKE
>  "%Quality Assurance%" ))
>
>
>
> If it evaluates to true, a message pops up that tells the user they
don't
> have permission to update a ticket that had a previous status of:
> $Dialog_Prev_Status$
>
>
>
> The problem is, this always evaluates to true if $GROUPS$ = "System
POC"
> regardless of the value of Dialog_Prev_Status.
>
>
>
> I unhid Dialog_Prev_Status to make sure, and I had a ticket where
> Dialog_Prev_Status = "Sys POC Working" and it still evaluated to true
and
> didn't allow the System POC to update the ticket.
>
>
>
> I'm sure it's something boneheaded that I'm missing but I can't wrap
my head
> around it.
>
>
>
> Michael A. McManus, SrA, USAF
>
> Remedy Developer
>
> HQ 754 ELSG/DOOH
>
> DSN: 596-6478/Comm: 334-416-6478
>
>
>
>
>
>   __20060125_______________________This posting was
> submitted with HTML in it___

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to