The TR value is also NULL if the field on the form was cleared. So in that case, the TR value is null, and the value has changed.
There's just too many variations and gotchas to make using the TR value worthwhile.
IMO. :-)
Thad Esser
Remedy Developer
| From: | "Grooms, Frederick W" <frederick.w.gro...@xo.com> |
| To: | arslist@ARSLIST.ORG |
| Date: | 04/14/2010 02:09 PM |
| Subject: | Re: TR vs DB sanity check please |
| Sent by: | "Action Request System discussion list(ARSList)" <arslist@ARSLIST.ORG> |
**
All fields in a Push Fields action are part of the push transaction yes, but for a standard modify of a form if they are not changed then the TR value is NULL.
From the Workflow Objects PDF
- Transaction Only—References the value of the field in the current transaction only. If the value is not changed in the transaction, it is considered to be $NULL$. If the operation is a delete, it is considered to be $NULL$. To specify a check of the transaction only, use the format 'TR.<field>' when you enter the field name in the Run If field.
- Database Only—References the value of the field in the database only. No check is made of the value in the current transaction. If the operation is a create operation, it is considered to be $NULL$. To specify a reference of the database only, use the format 'DB.<field>' when you enter the field name in the Run If field.
- Transaction and Database—References the value of the field in the current transaction and uses that value if changed. If not changed in the current transaction, references the value of the field in the database. To specify a reference of both the transaction and the database (in this order), use the format '<field>' when you enter the field name in the Run If field.
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Thad K Esser
Sent: Wednesday, April 14, 2010 3:58 PM
To: arslist@ARSLIST.ORG
Subject: Re: TR vs DB sanity check please
**
All fields that are specified in a push fields action are part of the TRansaction, and will therefore have a TR value, regardless of whether or not the value has changed.
Thad Esser
Remedy Developer
| From: | Tommy Morris <tommy.mor...@radioshack.com> |
| To: | arslist@ARSLIST.ORG |
| Date: | 04/14/2010 01:48 PM |
| Subject: | Re: TR vs DB sanity check please |
| Sent by: | "Action Request System discussion list(ARSList)" <arslist@ARSLIST.ORG> |
**
I understand how Rick put it that the TR is implied so you don’t have to specify it but why would including the identifier cause an erroneous result?
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Thad K Esser
Sent: Wednesday, April 14, 2010 3:44 PM
To: arslist@ARSLIST.ORG
Subject: Re: TR vs DB sanity check please
**
Tommy,
In some situations, your version will evaluate to true, even though nothing changed.
To truly detect if a value changed, its best to use:
'AssignedToTech' != 'DB.AssignedToTech'
Thad Esser
Remedy Developer
| From: | Tommy Morris <tommy.mor...@radioshack.com> |
| To: | arslist@ARSLIST.ORG |
| Date: | 04/14/2010 01:39 PM |
| Subject: | Re: TR vs DB sanity check please |
| Sent by: | "Action Request System discussion list(ARSList)" <arslist@ARSLIST.ORG> |
Instead of Runif: 'AssignedToTech' != 'AssignedToTech'
Make it Runif: 'TR.AssignedToTech' != 'DB.AssignedToTech'
-----Original Message-----
From: Action Request System discussion list(ARSList)
_attend WWRUG10 www.wwrug.com 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. *
_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
