You have two problems 1. Your Filter Run-If Qualification is firing on all modifications - TR will always be $NULL$ unless the value is changing and it's changing to something other than $NULL$...so when you are doing a compare of 'TR.Category' != 'Category' if the Category has not changed then your qualification would then be $NULL$ != 'Category'...which would always be true....unless Category was null...so you would want to either try 'TR.Category' != $NULL$ AND 'Category' != 'DB.Category' or you could just drop the first part off of that qualification.... 2. any time you use a setfield from current screen of $Field$ you will always get the current value. If you want to set the fields with the values in the DB then you will need to do a setfield from that same form doing a query where 'Request ID' = $Request ID$ and set the fields from that record return... Let me know if I confused you even more
_____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jase Brandon Sent: Monday, April 09, 2007 7:23 PM To: [email protected] Subject: Capture of Original CTI of Case/Task ** Hello Listers, I need to be able to capture the original CTI of a HelpDesk Case if it is changed. I thought this would be rather simple and wrote a filter using TR. Values with the below qualification. ('OrigCTIModified?' != "Yes") AND ('TR.Category' != 'Category' OR 'TR.Type' != 'Type' OR 'TR.Item' != 'Item') OR ('TR.Type' != 'Type' OR 'TR.Item' != 'Item') OR ('TR.Item' != 'Item') ***Above qual is so that if any of the three change, we can capture original cti*** My Set Fields Action was, if the qualification is met, then set the 'OrigCTIModified' Field to "Yes", so filter wouldn't fire if the CTI was changed again. In the same set fields action, I had already created four character fields and had them each set to 'Orig Category = $Category$, 'Orig Type' = $Type$ and 'Orig Type' = $TYPE$. Thought I was cruising right along, did some testing and discovered that the results I was getting in the 'Orig' fieds were the NEW CTI values, rather than the original values. I have been wracking my brain and can't figure out how to overcome this timing issue. Anyone have any thoughts? Thanks in Advance, :) Jase Brandon Remedy Administration/Development Customer Support Systems Group Desk - (615) - 320-4494 Cell - (334) - 318-5426 [EMAIL PROTECTED] DaVita Inc. __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
