What Fred is saying is avoid the escalation by including your normalization at time of save or in his second case at time of save of another form (with a non AR_ESCALATOR user). (Sorry Fred. Just wanted to make that a bit clearer).
The ONLY way to modify a record without changing the fields modifier and modified time is through the Merge API which is not doable by workflow. It is certainly doable with other methods like a Meta-Update script, your own code in a "binary" etc. ARS always performs the save when fields that set the "dirty bit" are set - even if they are set to the same value. Ie: db.f = 1; set fields f = 1; modification made. By rewriting your filters to diagnose that there are no changes rather than arbitrarily setting values to equal values, and by turning off the "Modified" flag on your trigger field, or by turning off the dirty bit at the end (a new filter that compares the fields you are modifying with the db.fields and if no changes turns off the dirty bit). This would still leave AR_ESCALATOR on those records that really were changed but (presumably) not on all records. Meta-Update by default does not issue the modify when nothing has changed. So certainly you would be able to do this with Meta-Update no problem. You also do not run into the filter limit. Cheers Ben Chernys Senior Software Architect Software Tool House Inc. Canada / Deutschland / Germany Mobile: +49 171 380 2329 GMT + 1 + [ DST ] Email: Ben.Chernys _AT_ softwaretoolhouse.com Web: www.softwaretoolhouse.com Check out Software Tool House's free Diary Editor. Meta-Update, our premium ARS Data tool, lets you automate your imports, migrations, in no time at all, without programming, without staging forms, without merge workflow. http://www.softwaretoolhouse.com/ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Grooms, Frederick W Sent: February-10-12 04:03 To: [email protected] Subject: Re: Escalation trigger filters without modifying records? If your "normalization" happens on every save of the record then are you having to run thru them on a schedule to update them because something somewhere else changed? i.e. If you are setting a Name field in Form AAA on save, are you trying to keep that Name field in sync with a Name somewhere else (like on Form BBB)? I would look at trying to detect when the source of Name (Form BBB) is changed and force the related records (Form AAA) to update at that time. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Brien Dieterle Sent: Thursday, February 09, 2012 6:13 PM To: [email protected] Subject: Escalation trigger filters without modifying records? I've got a lot of filters that do some "normalization" by setting some key fields via a lookup. This might be a bad idea, but I generally create escalations that do some tidying up-- they just blast through all the records and update a trigger field to trigger the modify filters. Having all the records "last modified by AR_ESCALATOR" is starting to irritate some of my colleagues, so I'd like to stop doing this. Any thoughts? I've tried several ways to get an escalation to trigger the modify actions without actually modifying the record-- without any success. I also definitely do not want to duplicate the code in the modify actions and copy them into the escalation. Thanks! Brien ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
