If NULL is a valid value then you will need to test for it explicitly. Your qualification will be undefined if your field is NULL which will result in that clause being FALSE. See the "NULL value, relational Algebra" section of the Workflow Objects guide. Your qualification should be more like:
'Billing_End_Date' != 'DB.Billing_End_Date' OR 'TR.Billing_End_Date' = $NULL$ Regards, Chuck Baldi On Mon, Sep 28, 2009 at 5:14 PM, Lyle Taylor <tayl...@ldschurch.org> wrote: > Perhaps it's a filter phasing issue. Probably any filters that update the > record (in order to trigger this filter) need to be named with `! at the end > to override filter phasing. > > Lyle > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] On Behalf Of PRUITT, CHRISTOPHER > Sent: Monday, September 28, 2009 3:11 PM > To: arslist@ARSLIST.ORG > Subject: Stumped - Need some fresh eyes > > We are stumped on a filter that does not want to fire correctly. > > > Here is the situation. > > We have an Asset record that has no billing end date set. > We set the Billing End Date to the current date/time along with other > fields and the filter with the Run If Qualification: 'Billing_End_Date' != > 'DB.Billing_End_Date' fires, as expected. This filter is just setting a > Audit Trail entry. > Right after that, on the same record about 3-5 seconds later we set the > Billing End Date back to NULL along with other fields and the same filter > does not fire. > > This is happening inside of a Filter Guide process that calls two different > Filter Guide. The first is Set the Asset to Inactive, the second is Set > Asset to Active along with new Data. All the data gets set correct including > the Billing End Date > > We do a move by first setting the data for the current Asset record that > has Active Billing to Inactive and Set the Billing End Date along with other > fields. > Later in the Filter Guide process we take that same record and update the > new data and reactivate the billing under the new person and set the Billing > End Date to NULL. It should work right? > > Now here is the rub. > > If we set the Asset record by itself to Inactive and Set the Billing End > Date the filter with the Run If Qualification: 'Billing_End_Date' != > 'DB.Billing_End_Date' fires. > Then is we set the Asset record by itself to active and Set the Billing End > Date to NULL the filter with the Run If Qualification: 'Billing_End_Date' != > 'DB.Billing_End_Date' fires. But not when we do it inside of a Guide. > > Anyone ever see this happen before? > > Our environment is: > Oracle 10g > Remedy 7.1.00 Build 200708221849 > SunOS 5.9 > > > Christopher Pruitt > HP Enterprise Services > Bank of America Account | CIA - Integrated Applications | IW Infrastructure > Team > 972.605.7702 office | christopher.pru...@hp.com > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum > Sponsor:rmisoluti...@verizon.net<sponsor%3armisoluti...@verizon.net>ARSlist: > "Where the Answers Are" > > > NOTICE: This email message is for the sole use of the intended > recipient(s) and may contain confidential and privileged information. Any > unauthorized review, use, disclosure or distribution is prohibited. If you > are not the intended recipient, please contact the sender by reply email and > destroy all copies of the original message. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum > Sponsor:rmisoluti...@verizon.net<sponsor%3armisoluti...@verizon.net>ARSlist: > "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
