I ran logging and the logs show it fails qualification with the TR.

I then removed the TR and physically changed some data on the record
and saved the record and my Filter did fire.

So I know my Filter qualification is correct.

The problem is how to trigger a Modify so my Filter will Fire.  The
escalation "setting" the field is not triggering a Modify.

The escalation is working because I have a blank field (field "A")
database field that I am setting and my Filter says if Field "A" is
NOT NULL then do the action.

Any ideas?

Thank you!!!



On 7/24/08, T. Dee <[EMAIL PROTECTED]> wrote:
> The escalation sets Field "A", but the Filter that is suppose to fire
> on MODIFY when Field "A" is != $NULL$ does not fire.  I have tried TR
> as well.
>
> In the escalation I tried to do a "set fields" and then I tried a
> "push fields", but both don't trigger a Modify.
>
> I'm running Windows 2003, SQL 2005.
>
>
>
> On Thu, Jul 24, 2008 at 7:03 PM, Leonard Neely - FOJ
> <[EMAIL PROTECTED]> wrote:
> > Does your filter fire when you manually set the value in field "A"?
> > Also, do you mind telling us what platform/version, Etc you are on?
> >
> > Thanks,
> >
> > Leonard
> >
> > -----Original Message-----
> > From: Action Request System discussion list(ARSList)
> > [mailto:[EMAIL PROTECTED] On Behalf Of T. Dee
> > Sent: Thursday, July 24, 2008 3:56 PM
> > To: [email protected]
> > Subject: Re: Question: Trigger a Modify ?
> >
> > I don't want to exclude AR_ESCALATOR - I want the Filter I have set to
> > run on MODIFY be triggered when the escalation does a set field to
> > field "A".
> >
> > The TR.fieldname != $NULL$ does not seem to work either.
> >
> > Thanks for your help!
> >
> >
> > On Thu, Jul 24, 2008 at 6:45 PM, Rick Cook <[EMAIL PROTECTED]> wrote:
> >> **
> >> You could list an exclusion for the "AR_ESCALATOR" user from the Run If on
> >> your Filter.
> >>
> >> Rick
> >>
> >> On Thu, Jul 24, 2008 at 3:38 PM, T. Dee <[EMAIL PROTECTED]> wrote:
> >>>
> >>> I have an escalation running that is setting field "A" with a value -
> >>> this works.  I also have a filter that fires on MODIFY if field "A" is
> >>> NOT NULL.  The problem is the filter is not firing when my escalation
> >>> runs.  Is there a way to "force" a modify after the escalation runs so
> >>> my filter will run?
> >>>
> >>> THANKS!!!!!!!!!!!
> >>>
> >>>
> >>>
> > ____________________________________________________________________________
> > ___
> >>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> >>> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> >>
> >> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> >> html___
> >
> > ____________________________________________________________________________
> > ___
> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> >
> > _______________________________________________________________________________
> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> >
>

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

Reply via email to