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: [email protected]
> 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: [email protected]
> 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"
