[rt-users] SLA extension with prior Scrip setting SLA CF

[Mark D. Nagel]

We ran into a problem that I think may be solvable with use of TransactionBatch, but may
require changes to the SLA extension.  Or perhaps not.  Thus this question, which is....

We are using the ExtractCustomFieldValues extension to indicate to RT the initial setting
of some fields, including the SLA field, depending on various factors examined in our
procmail pre-filter.  What we found was that the field was set, then the SLA scrip resets
it to the default queue value.  It seems that this is because all the conditions run first
telling the SLA scrip to set the default value, which it does even though the value had
been set previously. 

So....  what would be the recommended solution here to make sure this doesn't happen?  I
could move the ExtractCFValues Scrip to the bottom, which seems like it would work, but it
would be nice if the SLA Scrip realized it doesn't actually need to set the CF once it was
set.  If we change both to TransactionBatch, this could work, but I assume this would
still require some changes to the SLA condition logic.

Thanks,
Mark

-- 
Mark D. Nagel, CCIE #3177 <mnagel at willingminds.com>
Principal Consultant, Willing Minds LLC (http://www.willingminds.com)
cell: 949-279-5817, desk: 714-495-4001, fax: 714-646-8277

** For faster support response time, please
** email support at willingminds.com or call 714-495-4000