.
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Dave.ARSList
Sent: Thursday, October 04, 2007 3:08 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Andy,
I don't think what you said is true - ( 'AssignedConfigTech
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Thad, I'm glad there's at least one person in the
world who has settled on the same rule regarding use
of TR values. Don't!
Cause it's not necessary. There's no qualification you
can't build without using TR. It's nothing but
trouble.
TR
discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David
Sent: Wednesday, October 03, 2007 9:09 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
DB.Field has to query the database. By definition it is the data that's
stored in the field in the database.
From my
cc:
Request System Subject: Re: Filter Problem
discussion
PROTECTED] To:
arslist@ARSLIST.ORG
Sent by: Action cc:
Request System Subject: Re: Filter
Problem
discussion
list(ARSList)
[EMAIL PROTECTED
enough,
they're yours.-- Richard
Bach
Mayfield, Andy L. [EMAIL PROTECTED]
Sent by: Action Request System discussion
list(ARSList)
arslist@ARSLIST.ORG
10/03/2007 07:55 AM
Please respond to
arslist@ARSLIST.ORG
To
arslist@ARSLIST.ORG
cc
Subject
Re: Filter Problem
(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David
Sent: Wednesday, October 03, 2007 9:09 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
DB.Field has to query the database. By definition it is the data that's
stored in the field in the database.
From my
-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Misi Mladoniczky
Sent: Thursday, October 04, 2007 6:31 AM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Hi,
You are correct in the assumption that TR-values can save a little bit on
performance
.
Jason
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David
Sent: Wednesday, October 03, 2007 9:09 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
DB.Field has to query the database. By definition
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Misi Mladoniczky
Sent: Thursday, October 04, 2007 6:31 AM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Hi,
You are correct in the assumption that TR-values can save
: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Misi Mladoniczky
Sent: Thursday, October 04, 2007 6:31 AM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Hi,
You are correct in the assumption that TR-values can save a little bit on
performance
Axton:
Take it as my personal preference that I don't use TR
values, so I am blind by choice to the existence of
TR. Not that I never mingled with this guy TR. I bid
goodbye to TR after huge issues using it in ITSM 6.
Especially with the big forms.
Funny thing is I didn't say one day now I stop
@ARSLIST.ORG
Subject: Re: Filter Problem
A flaw, maybe. The solutions I see to address this would be some type
of record locking to prevent updates based on stale data. I guess
there could be a couple of approaches to this:
- return an error if you attempt to update and the data you are using
, 2007 12:43 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
A flaw, maybe. The solutions I see to address this would be some type
of record locking to prevent updates based on stale data. I guess
there could be a couple of approaches to this:
- return an error if you attempt to update
Skilled Professional
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Axton
Sent: Thursday, October 04, 2007 12:43 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
A flaw, maybe. The solutions I see to address
.-- Richard
Bach
Axton [EMAIL PROTECTED]
Sent by: Action Request System discussion list(ARSList)
arslist@ARSLIST.ORG
10/04/2007 11:26 AM
Please respond to
arslist@ARSLIST.ORG
To
arslist@ARSLIST.ORG
cc
Subject
Re: Filter Problem
I only see the db call if using DB. I chopped the log lines so
, 2007 6:09 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Thad, I'm glad there's at least one person in the
world who has settled on the same rule regarding use
of TR values. Don't!
Cause it's not necessary. There's no qualification you
can't build without using TR. It's nothing
@ARSLIST.ORG
cc
Subject
Re: Filter Problem
Hi,
You are correct in the assumption that TR-values can save a little bit on
performance.
The server looks through the run-if-qualification of all filters.
If anywhere there is a 'Field' or 'DB.Field', the server will need fetch
Professional
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Axton
Sent: Thursday, October 04, 2007 12:43 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
A flaw, maybe. The solutions I see to address this would
: Thursday, October 04, 2007 12:43 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
A flaw, maybe. The solutions I see to address this would be some type
of record locking to prevent updates based on stale data. I guess
there could be a couple of approaches to this:
- return
/2007 03:31 AM
Please respond to
arslist@ARSLIST.ORG
To
arslist@ARSLIST.ORG
cc
Subject
Re: Filter Problem
Hi,
You are correct in the assumption that TR-values can save a little bit on
performance.
The server looks through the run-if-qualification of all filters
=0AHueytown, AL 35=
0231835=0D=0AUSA
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20070626T132537Z
END:VCARD
--
View this message in context:
http://www.nabble.com/Filter-Problem-tf4558880.html#a13047833
Sent from the ARS (Action Request System) mailing list archive at Nabble.com
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Andy,
I don't think what you said is true - ( 'AssignedConfigTech' != $NULL$ )
AND ( 'DB.AssignedConfigTech' != 'TR.AssignedConfigTech')
If I am reading the statement correctly, the filter should not fire unless
the 'AssignedConfigTech' is changed
, nothing changed.
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Dave.ARSList
Sent: Thursday, October 04, 2007 3:08 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Andy,
I don't think what you said is true
respond to
arslist@ARSLIST.ORG
To
arslist@ARSLIST.ORG
cc
Subject
Re: Filter Problem
Hi,
You are correct in the assumption that TR-values can save a little bit
on
performance.
The server looks through the run-if-qualification of all filters.
If anywhere there is a 'Field
/2007 01:36 PM
Please respond to
arslist@ARSLIST.ORG
To
arslist@ARSLIST.ORG
cc
Subject
Re: Filter Problem
Hi Dave,
The problem here is that a TR value van be NULL, but is still part of the
transaction.
All fields not part of the transaction will also have a TR value of NULL.
The statement
@ARSLIST.ORG
Sent: Thu Oct 04 17:25:45 2007
Subject: Re: Filter Problem
**
Dave,
Misi is correct in saying that this statement is wrong: Only new or changed
field values are part of a transaction.
TR values do NOT detect change. The only reliable way to detect change is to
compare the current
Of Joe D'Souza
Sent: Tuesday, October 02, 2007 10:57 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Yes the TR value is NULL if there is no modification even if there is a DB
value to that field..
This is how it works.. when you are submitting a new record
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Tuesday, October 02, 2007 10:57 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Yes the TR value is NULL if there is no modification even if there is a
DB
] On Behalf Of Joe D'Souza
Sent: Tuesday, October 02, 2007 10:57 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Yes the TR value is NULL if there is no modification even if there is a
DB
value to that field..
This is how it works.. when you are submitting a new record
@ARSLIST.ORG
Subject: Re: Filter Problem
I thought everyone was saying that if I set a field to NULL (that
previously had a value), the TR value would NOT be NULL?
I am getting confused. I may need to take a break for coffee and a
cigarette to clear my head (-:
Andy L. Mayfield
Sr. System
Company
Office: 8-226-1805
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Axton
Sent: Wednesday, October 03, 2007 8:41 AM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
This one that probably often trips people up
Power Company
Office: 8-226-1805
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David
Sent: Wednesday, October 03, 2007 9:16 AM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Andy,
As Axton said TR.field really
Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Mayfield, Andy L.
Sent: Wednesday, October 03, 2007 10:55 AM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
OK, I think after a few cups of coffee I am now able to comprehend this.
TR.Field
by: Action Request System discussion list(ARSList)
arslist@ARSLIST.ORG
10/03/2007 07:55 AM
Please respond to
arslist@ARSLIST.ORG
To
arslist@ARSLIST.ORG
cc
Subject
Re: Filter Problem
OK, I think after a few cups of coffee I am now able to comprehend this.
TR.Field != $NULL$ should fire anytime
L.
Sent: Wednesday, October 03, 2007 10:55 AM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
OK, I think after a few cups of coffee I am now able to comprehend this.
TR.Field != $NULL$ should fire anytime the field is changed, unless it is
actually set to NULL.
That is rather confusing
, 2007 6:09 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Thad, I'm glad there's at least one person in the
world who has settled on the same rule regarding use
of TR values. Don't!
Cause it's not necessary. There's no qualification you
can't build without using TR. It's nothing but
trouble
)
[mailto:[EMAIL PROTECTED] Behalf Of Jason Miller
Sent: Wednesday, October 03, 2007 11:19 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
While the TR is confusing isn't there a performance benefit? If I remember
correctly a TR check will not run a query against the database (I haven't
So does TR have any purpose?
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Wednesday, October 03, 2007 8:29 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
**
I think neither runs any more queries than the other
PROTECTED] (Wireless)
- Original Message -
From: Action Request System discussion list(ARSList) arslist@ARSLIST.ORG
To: arslist@ARSLIST.ORG arslist@ARSLIST.ORG
Sent: Thu Oct 04 00:03:26 2007
Subject: Re: Filter Problem
**
So does TR have any purpose?
From: Action Request System
, David
Sent: Wednesday, October 03, 2007 9:09 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
DB.Field has to query the database. By definition it is the data that's stored
in the field in the database.
From my Performance Tuning class several years ago, Lincoln noted
OK, I am stumped. I have a filter firing that should not be.
I have a filter that sends a notification based on the qualification
statement:
( 'AssignedConfigTech' != $NULL$ ) AND ( 'DB.AssignedConfigTech' !=
'TR.AssignedConfigTech')
If I am reading the statement correctly, the
$ ) AND ( 'DB.AssignedConfigTech' !=
'AssignedConfigTech')
Regards
Atul
- Original Message -
From: Mayfield, Andy L.
To: arslist@ARSLIST.ORG
Subject: Filter Problem
Date: Tue, 2 Oct 2007 18:04:16 -0500
**
OK, I am stumped. I have a filter firing that should not be.
I have a filter
'DB.AssignedConfigTech' != $NULL$
thus the filter fires.
This qual should work
( 'AssignedConfigTech' != $NULL$ ) AND ( 'DB.AssignedConfigTech' !=
'AssignedConfigTech')
Regards
Atul
- Original Message -
From: Mayfield, Andy L.
To: arslist@ARSLIST.ORG
Subject: Filter Problem
Date
What would happen if someone typed the same value in the field (or select
the same value) will TR value be NULL in that case?
- Original Message -
From: YHK
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Date: Tue, 2 Oct 2007 19:41:44 -0400
** Just
)
[mailto:[EMAIL PROTECTED] On Behalf Of Atul Vohra
Sent: Tuesday, October 02, 2007 4:55 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
**
What would happen if someone typed the same value in the field
(or select the same value) will TR
*Sent:* Tuesday, October 02, 2007 4:55 PM
*To:* arslist@ARSLIST.ORG
*Subject:* Re: Filter Problem
**
What would happen if someone typed the same value in the field (or select
the same value) will TR value be NULL in that case?
- Original Message -
From: YHK
To: arslist
: Filter Problem
You need to be careful that the AssignedConfigTech can't be set to NULL.
If it is the TR.AssignedConfigTech will resolve to NULL.
Dave
--
[EMAIL PROTECTED] (Wireless)
- Original Message -
From: Action Request System discussion list(ARSList
list(ARSList) arslist@ARSLIST.ORG
To: arslist@ARSLIST.ORG arslist@ARSLIST.ORG
Sent: Tue Oct 02 21:57:09 2007
Subject: Re: Filter Problem
I did not realize that the TR. value would = $NULL$ just because it was
not being modified, when it already contained a value. It makes sense
now that I think
Hi Andy,
I am newbie to remedy..but as far as i see..the filter will fire..lets analyze
this.
Lets say AssignedConfigTech=ALEX, DB.AssignedConfigTech=James. Now lets
consider your scenario where the form is saved without a change being made the
‘AssignedConfigTech’ field. So lets put values
)
[mailto:[EMAIL PROTECTED] Behalf Of Mayfield, Andy L.
Sent: Tuesday, October 02, 2007 9:57 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
I did not realize that the TR. value would = $NULL$ just because it was not
being modified, when it already contained a value. It makes sense now that I
51 matches
Mail list logo
