Thank you Greg,
that didnt seem to remedy the issue. Error fires up on any status now...
On Fri, May 20, 2011 at 12:03 PM, Greg Donalson <cdonal...@slb.com> wrote:
> **
>
> Hi Gerard,
>
>
>
> Since it is a new request, the DB.Status is NULL. I would make the Run If
> be: (('DB.Status' < "Resolved") OR ('DB.Status' = "Cancelled") OR
> (‘DB.Status’ = $NULL$)) AND ('Status' = "Closed")
>
>
>
> Hope this fixes it. Thanks!
>
>
>
> Greg
>
>
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> arslist@ARSLIST.ORG] *On Behalf Of *Gerard Lafontant
> *Sent:* Friday, May 20, 2011 10:59 AM
> *To:* arslist@ARSLIST.ORG
> *Subject:* needs immediate help on this query....
>
>
>
> ** All,
>
> Can anyone tell me what am i missing or is wrong from this query that's
> causing the filter not to fire (by pass) on new request; and only fires on
> modified existing request. Basically, i'm forcing user to keep away from
> using 'Closed' Status resolution and push them to use the 'Resolved' status
> upon closing a ticket.
>
> (('DB.Status' < "Resolved") OR ('DB.Status' = "Cancelled")) AND ('Status' =
> "Closed")
>
> Status Value Order:
> New=0
> Assigned=1
> In Progress=2
> Pending=3
> Resolved=4
> Closed=5
> Cancelled=6 _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers
> Are"_
>
> _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
