Hi,
The TR values are pretty useless.
The reason is that a TR value can be set to NULL either by a change to NULL or
by not changing the field at all. In the latter case the field will retain the
value in the database after the transaction, but in the first case the NULL
will be written to the database.
This is how you check for a field data change:
('Field' != 'DB.Field')
Sometimes you want to trigger things only on a non-null-change on an optional
field in which case you write:
('Field' != 'DB.Field' AND 'Field' != $NULL$)
The TR values can be used as a lazy, and non exact, way to trigger a few things:
('TR.Assigned To' != $NULL$) => Send notification to "new" assignee
It is sometimes possible that the notification will be sent without the data
actually being changed, in which case you can extend the qualification. But in
that case it is as easy to use 'Field' as 'TR.Field'.
These are equivalent:
('Field' != 'DB.Field' AND 'Field' != $NULL$)
('TR.Field' != 'DB.Field' AND 'TR.Field' != $NULL$)
Note that Push-Fields typically sends transactional values even without a
change, but a normal 'Save' by the user will send TR-values only for those
fields which has been changed.
Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> Some wonder why TR was built others say it works fine. I thought I had a good
> handle on TR but now reading the differing opinions I am questing my
> understanding of TR.
>
> Some posts indicate it is completely useless and can't be trusted. Some other
> indicate like a weapon as long as you treat it with respect and know how to
> you it you'll be fine.
>
> So off the the archives I went:
> http://ars-action-request-system.1.n7.nabble.com/TR-vs-DB-sanity-check-please-tp99981p99993.html
>
> Doug set it straight in 2010. After rereading his post I am questioning the
> purpose of TR.
>
> QUOTE: 'A' != 'DB.A' is all the testing you need to see if the value has
> changed
>
> If DB all that is needed what is a valid use case for having TR. Not one that
> can be down with TR or DB but what is that TR provides that cannot be done
> otherwise?
>
> Jason
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
