I'm with Fred. If the two filters are firing within the one transaction (setting the billing end date, and then setting it back to NULL), I believe the DB.xxx check for the second filter will still be referring to the original DB value, as at the start of the transaction (NULL). By using the Application-Release-Pending Run Process action between the two filters, you will force the first set fields to update the database, and the next filter should detect the different value.
Alternatively, you could use a temp field to achieve the same thing. Regards, Matt On Tue, Sep 29, 2009 at 7:32 AM, Lyle Taylor <[email protected]> wrote: > ** > > Actually, that would fire any time the Billing_End_Date didn’t change or > was set to NULL (TR.Billing_End_Date will always be NULL unless the value is > being changed to something non-null). He doesn’t need to determine when > it’s null, just if it is being changed. In that case, since it does > correctly fire in one case (where it’s null in the DB but no in the updated > record), it should also fire the other way around as well. If it doesn’t, > then that would probably be a bug and not be related to the NULL value > relational Algebra. I think the relational Algebra discussion relates more > to searches and may not apply here in this context. (I could be wrong on > that point, but my first point above is correct.) > > > > Lyle > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Charles Baldi > *Sent:* Monday, September 28, 2009 3:23 PM > *To:* [email protected] > *Subject:* Re: Stumped - Need some fresh eyes > > > > ** > > 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 <[email protected]> > 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: > [email protected]] On Behalf Of PRUITT, CHRISTOPHER > Sent: Monday, September 28, 2009 3:11 PM > To: [email protected] > 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 | [email protected] > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum > Sponsor:[email protected]<sponsor%[email protected]>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:[email protected]<sponsor%[email protected]>ARSlist: > "Where the Answers Are" > > > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers > Are"_ > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers > Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
