Re: TR, DB, and nothing
Hi,
It only states that TR should be used to check the value of a transaction.
It does not describe what a transaction-value is.
It will allways suffice to do these tests:
1. check for any change:
('Field' != 'DB.Field')
2. check for a change to non NULL value:
('Field' != 'DB.Field' AND 'Field' != $NULL$)
If you need to check fields against a specific value as well as finding a
change, use something like this:
('Status' != 'DB.Status' AND 'Status' = Assigned)
This is all you really need to know!
We have also discussed potential performace improvements with checking
TR-values only. I think we have ruled out this as significant. Do not use
the TR-values.
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at http://rrr.se.
Michael,
I read what Dave said -
Following is taken straight from page 36 of Work-Flow Objects-700.pdf
We have a few filters that need to fire ONLY if that particular value is
changed in a given transaction and it fires as intended and doesn't fire
when it shouldn't. It works fine for me.
For filters, you can specify whether the qualification is to reference
field values in the transaction only, in the database only, or in both:
To check the value for the transaction only, enter the field name as
'TR.field' (for example, 'TR.Submitter').
To check the value in the database only, enter the field name as
'DB.field'
(for example, 'DB.Submitter').
To check the value for the transaction first and then check the
database if a new value is not found in the transaction, enter the field
name with no prefix.
If the documentaion is not flawed then 'FieldName' = Current value of
the field is not accurate 'cos (To check the value for the transaction
first and then check the database if a new value is not found in the
transaction, enter the field name with no prefix.)
If you are right then the documentation is not proper..
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of McManus Michael A SSgt HQ 754
ELSG/DOMH
Sent: Thursday, October 04, 2007 4:01 PM
To: arslist@ARSLIST.ORG
Subject: Re: TR, DB, and nothing
'FieldName' = Current value of the field
'TR.FieldName' = Current value of the field if it has changed, else the
value is null.
'DB.FieldName' = Value stored in the database. Obviously, this value
does not exist on submit.
Michael A. McManus, SSgt, USAF
Remedy Developer
HQ 754 ELSG/DOMH
DSN: 596-6478 / Comm: 334-416-6478
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Cupp, Michael E CTR USAF
AFRL/RYOD
Sent: Thursday, October 04, 2007 3:58 PM
To: arslist@ARSLIST.ORG
Subject: TR, DB, and nothing
Can someone explain the difference between the following:
'FieldName'
'TR.FieldName'
'DB.FieldName'
Are there other prefixes out there that may be of use?
If the DB. is what I think it is, it's something I've asked for, but was
told didn't exist, so I have had to do extensive coding around it
(Creating a dup field, setting it via work flow, comparing 2 field
values, etc).
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete the
original. Any other use of the email by you is prohibited.
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where
the Answers Are
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the
Answers Are
Re: TR, DB, and nothing
'FieldName' = Current value of the field 'TR.FieldName' = Current value of the field if it has changed, else the value is null. 'DB.FieldName' = Value stored in the database. Obviously, this value does not exist on submit. Michael A. McManus, SSgt, USAF Remedy Developer HQ 754 ELSG/DOMH DSN: 596-6478 / Comm: 334-416-6478 -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Cupp, Michael E CTR USAF AFRL/RYOD Sent: Thursday, October 04, 2007 3:58 PM To: arslist@ARSLIST.ORG Subject: TR, DB, and nothing Can someone explain the difference between the following: 'FieldName' 'TR.FieldName' 'DB.FieldName' Are there other prefixes out there that may be of use? If the DB. is what I think it is, it's something I've asked for, but was told didn't exist, so I have had to do extensive coding around it (Creating a dup field, setting it via work flow, comparing 2 field values, etc). Thanks! M ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: TR, DB, and nothing
Well there has been extensive discussion over the last few days on the subject. TR and DB are prefixes that can be used in filter qualifiers to check for changes. 'TR.Field' is a transactional value associated with a field. It can be used to detect when a change happens to a field. It can give seemingly inconsistent results at times though. 'DB.Field' references the value of the field in the database. 'Field' is basically the value of a field when the record is created or modified. These can be used in differing qualifiers with filters. To check that a value has changed most folks that have been around for several years will use 'Field' != 'DB.Field' If the filter should only trigger if the field is not NULL then use 'Field' != $BILL$ AND 'Field' != 'DB.Field' Dave -- [EMAIL 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 16:58:23 2007 Subject: TR, DB, and nothing Can someone explain the difference between the following: 'FieldName' 'TR.FieldName' 'DB.FieldName' Are there other prefixes out there that may be of use? If the DB. is what I think it is, it's something I've asked for, but was told didn't exist, so I have had to do extensive coding around it (Creating a dup field, setting it via work flow, comparing 2 field values, etc). Thanks! M ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: TR, DB, and nothing
Exactly... Filters only, and the TR/DB values are only available as part of the Run If of the filter. They don't exist for any of the actions. Thad Esser Remedy Developer Argue for your limitations, and sure enough, they're yours.-- Richard Bach Wheeler, Dylan [EMAIL PROTECTED] Sent by: Action Request System discussion list(ARSList) arslist@ARSLIST.ORG 10/04/2007 02:04 PM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: TR, DB, and nothing To add, this only works for filters, AL is client side so no DB comparison is available, which is why you have to do a set fields on a temp field to compare. Check the 6.3 basic dev guide page 491 for more details. Dylan -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of McManus Michael A SSgt HQ 754 ELSG/DOMH Sent: Thursday, October 04, 2007 2:01 PM To: arslist@ARSLIST.ORG Subject: Re: TR, DB, and nothing 'FieldName' = Current value of the field 'TR.FieldName' = Current value of the field if it has changed, else the value is null. 'DB.FieldName' = Value stored in the database. Obviously, this value does not exist on submit. Michael A. McManus, SSgt, USAF Remedy Developer HQ 754 ELSG/DOMH DSN: 596-6478 / Comm: 334-416-6478 -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Cupp, Michael E CTR USAF AFRL/RYOD Sent: Thursday, October 04, 2007 3:58 PM To: arslist@ARSLIST.ORG Subject: TR, DB, and nothing Can someone explain the difference between the following: 'FieldName' 'TR.FieldName' 'DB.FieldName' Are there other prefixes out there that may be of use? If the DB. is what I think it is, it's something I've asked for, but was told didn't exist, so I have had to do extensive coding around it (Creating a dup field, setting it via work flow, comparing 2 field values, etc). Thanks! M ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are This message and any attachments are for the intended recipient(s) only and may contain privileged, confidential and/or proprietary information about Downey Savings or its customers, which Downey Savings does not intend to disclose to the public. If you received this message by mistake, please notify the sender by reply e-mail and delete the message and attachments. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are ***IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.*** ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: TR, DB, and nothing
To add my 2 cents also: the TR and DB prefixes can ONLY be used on the Run If condition of the filter. Not Set Fields, not Push Fields, etc... Mark //SIGNED// MARK A. WORLEY, Contractor, 2 SOS/SYOS Remedy ARS Support, SAIC Commercial: (402) 294-8226 DSN: 271-8226 mailto:[EMAIL PROTECTED] -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Wheeler, Dylan Sent: Thursday, October 04, 2007 16:05 To: arslist@ARSLIST.ORG Subject: Re: TR, DB, and nothing To add, this only works for filters, AL is client side so no DB comparison is available, which is why you have to do a set fields on a temp field to compare. Check the 6.3 basic dev guide page 491 for more details. Dylan -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of McManus Michael A SSgt HQ 754 ELSG/DOMH Sent: Thursday, October 04, 2007 2:01 PM To: arslist@ARSLIST.ORG Subject: Re: TR, DB, and nothing 'FieldName' = Current value of the field 'TR.FieldName' = Current value of the field if it has changed, else the value is null. 'DB.FieldName' = Value stored in the database. Obviously, this value does not exist on submit. Michael A. McManus, SSgt, USAF Remedy Developer HQ 754 ELSG/DOMH DSN: 596-6478 / Comm: 334-416-6478 -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Cupp, Michael E CTR USAF AFRL/RYOD Sent: Thursday, October 04, 2007 3:58 PM To: arslist@ARSLIST.ORG Subject: TR, DB, and nothing Can someone explain the difference between the following: 'FieldName' 'TR.FieldName' 'DB.FieldName' Are there other prefixes out there that may be of use? If the DB. is what I think it is, it's something I've asked for, but was told didn't exist, so I have had to do extensive coding around it (Creating a dup field, setting it via work flow, comparing 2 field values, etc). Thanks! M ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are This message and any attachments are for the intended recipient(s) only and may contain privileged, confidential and/or proprietary information about Downey Savings or its customers, which Downey Savings does not intend to disclose to the public. If you received this message by mistake, please notify the sender by reply e-mail and delete the message and attachments. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: TR, DB, and nothing
To add, this only works for filters, AL is client side so no DB comparison is available, which is why you have to do a set fields on a temp field to compare. Check the 6.3 basic dev guide page 491 for more details. Dylan -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of McManus Michael A SSgt HQ 754 ELSG/DOMH Sent: Thursday, October 04, 2007 2:01 PM To: arslist@ARSLIST.ORG Subject: Re: TR, DB, and nothing 'FieldName' = Current value of the field 'TR.FieldName' = Current value of the field if it has changed, else the value is null. 'DB.FieldName' = Value stored in the database. Obviously, this value does not exist on submit. Michael A. McManus, SSgt, USAF Remedy Developer HQ 754 ELSG/DOMH DSN: 596-6478 / Comm: 334-416-6478 -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Cupp, Michael E CTR USAF AFRL/RYOD Sent: Thursday, October 04, 2007 3:58 PM To: arslist@ARSLIST.ORG Subject: TR, DB, and nothing Can someone explain the difference between the following: 'FieldName' 'TR.FieldName' 'DB.FieldName' Are there other prefixes out there that may be of use? If the DB. is what I think it is, it's something I've asked for, but was told didn't exist, so I have had to do extensive coding around it (Creating a dup field, setting it via work flow, comparing 2 field values, etc). Thanks! M ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are This message and any attachments are for the intended recipient(s) only and may contain privileged, confidential and/or proprietary information about Downey Savings or its customers, which Downey Savings does not intend to disclose to the public. If you received this message by mistake, please notify the sender by reply e-mail and delete the message and attachments. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: TR, DB, and nothing
Almost... 'FieldName' = The most current value of the field 'TR.FieldName' = The TRansaction value of the field. Basically, any field that is in the SET clause of the SQL update statement. 'DB.FieldName' = The value stored in the database. Thad Esser Remedy Developer Argue for your limitations, and sure enough, they're yours.-- Richard Bach McManus Michael A SSgt HQ 754 ELSG/DOMH [EMAIL PROTECTED] Sent by: Action Request System discussion list(ARSList) arslist@ARSLIST.ORG 10/04/2007 02:01 PM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: TR, DB, and nothing 'FieldName' = Current value of the field 'TR.FieldName' = Current value of the field if it has changed, else the value is null. 'DB.FieldName' = Value stored in the database. Obviously, this value does not exist on submit. Michael A. McManus, SSgt, USAF Remedy Developer HQ 754 ELSG/DOMH DSN: 596-6478 / Comm: 334-416-6478 -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Cupp, Michael E CTR USAF AFRL/RYOD Sent: Thursday, October 04, 2007 3:58 PM To: arslist@ARSLIST.ORG Subject: TR, DB, and nothing Can someone explain the difference between the following: 'FieldName' 'TR.FieldName' 'DB.FieldName' Are there other prefixes out there that may be of use? If the DB. is what I think it is, it's something I've asked for, but was told didn't exist, so I have had to do extensive coding around it (Creating a dup field, setting it via work flow, comparing 2 field values, etc). Thanks! M ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are ***IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.*** ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: TR, DB, and nothing
Michael, I read what Dave said - Following is taken straight from page 36 of Work-Flow Objects-700.pdf We have a few filters that need to fire ONLY if that particular value is changed in a given transaction and it fires as intended and doesn't fire when it shouldn't. It works fine for me. For filters, you can specify whether the qualification is to reference field values in the transaction only, in the database only, or in both: To check the value for the transaction only, enter the field name as 'TR.field' (for example, 'TR.Submitter'). To check the value in the database only, enter the field name as 'DB.field' (for example, 'DB.Submitter'). To check the value for the transaction first and then check the database if a new value is not found in the transaction, enter the field name with no prefix. If the documentaion is not flawed then 'FieldName' = Current value of the field is not accurate 'cos (To check the value for the transaction first and then check the database if a new value is not found in the transaction, enter the field name with no prefix.) If you are right then the documentation is not proper.. -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of McManus Michael A SSgt HQ 754 ELSG/DOMH Sent: Thursday, October 04, 2007 4:01 PM To: arslist@ARSLIST.ORG Subject: Re: TR, DB, and nothing 'FieldName' = Current value of the field 'TR.FieldName' = Current value of the field if it has changed, else the value is null. 'DB.FieldName' = Value stored in the database. Obviously, this value does not exist on submit. Michael A. McManus, SSgt, USAF Remedy Developer HQ 754 ELSG/DOMH DSN: 596-6478 / Comm: 334-416-6478 -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Cupp, Michael E CTR USAF AFRL/RYOD Sent: Thursday, October 04, 2007 3:58 PM To: arslist@ARSLIST.ORG Subject: TR, DB, and nothing Can someone explain the difference between the following: 'FieldName' 'TR.FieldName' 'DB.FieldName' Are there other prefixes out there that may be of use? If the DB. is what I think it is, it's something I've asked for, but was told didn't exist, so I have had to do extensive coding around it (Creating a dup field, setting it via work flow, comparing 2 field values, etc). This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
