James, Can't say I have heard anyone saying not to use it. Comparing the current value on the database against the current value on the client can be very useful when you want to take an action only when the field value changes.
If TR.Status !=DB.Status is like saying if the Status changes If TR.Status !=DB.Status and TR.Status = "Closed" is like saying when the ticket is closed Now I have heard that in some cases the TR causes some issues and it is best just to leave it off If Status !=DB.Status and Status = "Closed" again iss like saying when the ticket is closed and when I create a filter with a comparison, this is the format I use. Hope this helps Mark -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of James Smith Sent: Thursday, May 08, 2014 11:22 AM To: arslist@ARSLIST.ORG Subject: Transactional (TR) and Database (DB) Hi List, We can achieve things without using TR and DB values in a filter by just using Field but I do not understand why they have been developed to use? I have heard from many remedy developers like Misi and BMC who suggest not to use TR and DB in Run If qualification of a filter but why? Why it is not recommended to use TR and DB values? What if I use TR.Field=DB.Field? Will it yield a correct result? In BMC documentation also they have not given any example where they used TR and DB together in a qualification. Appreciate your thoughts! Cheers, James _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
