[rt-users] Transaction/Scrip ordering and DB Caching.

[Jesse Vincent]

On Sep 8, 2008, at 8:40 PM, Todd Chapman wrote:

> Jesse,
>
> The problem was the custom field was added in the commit stage of  
> the action, but template rendering is completed in the prepare  
> phase. Once I moved the custom field code to the prepare stage  
> everything started working. Unfortunately I was using the  
> ExtractCustomFieldValues extension, so I had to write my own code  
> that used the prepare phase.
>
> Thanks!
>
You might have also been able to get away with moving your autoreply  
to TransactionBatch.

-j

> -Todd
>
> On Mon, Sep 8, 2008 at 6:53 PM, Jesse Vincent  
> <jesse at bestpractical.com> wrote:
>
> On Sep 8, 2008, at 3:05 PM, Todd Chapman wrote:
>
>> I am having a problem trying to figure out how to have a scrip run  
>> before the Autoreply scrip and add a custom field value and use  
>> that custom field value in the Autoreply template.
>>
>> I know that scrips are run in order of description. Should the  
>> custom field value (fetched using ->FirstCustomFieldValue) be  
>> visible in the Autoreply template? Is DB caching possibly the  
>> problem?
>>
>> This is for RT 3.6.3. Any help is appreciated.
>
> Before spending a lot of time beating your head against this, can  
> you test on something more current? There has been a lot of cleanup  
> in that codepath since then.
>
> -j
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20080908/4ed07b13/attachment.htm>