There is no DB.Status yet on new? Maybe add some 'on create' logic? Mark
Mark Blankenship Business Analyst Office of Information Management & Analysis The University of Texas at Austin (512)475-7820 m...@austin.utexas.edu<mailto:m...@austin.utexas.edu> 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<http://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"
