<br><br><div class="gmail_quote">On Sun, Oct 24, 2010 at 11:45 PM, Jesse Vincent <span dir="ltr"><<a href="mailto:jesse@bestpractical.com">jesse@bestpractical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
<br>
<br>
On Sun 24.Oct'10 at 11:57:10 -0400, Todd Chapman wrote:<br>
> Is there some reason extractcustomfieldvalues does it's work in Commit instead<br>
> of Prepare?<br>
<br>
</div>...because that's when you're supposed to actually do the work. What<br>
you're looking for is a sensible request and is something we intend to<br>
address when we get Scrips' replacement out the door.<br></blockquote><div><br></div><div>Interesting that the work of evaluating the template is done in Prepare. </div><div><br></div><div>What is the status of the scrips replacement? It a preview available on the github repo?</div>
<div><br></div><div>Also, will scrips for objects other that tickets be supported?</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> I would think it fairly common to want to use { $Ticket-><br>
> FirstCustomFieldValue('foo') } in email templates, but<br>
> since extractcustomfieldvalues does it's work in Commit and the templates are<br>
> evaulated in Prepare, even scrip ordering doesn't make this possible.<br>
><br>
> Thanks.<br>
><br>
> -Todd<br>
<br>
</div>> _______________________________________________<br>
> List info: <a href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel" target="_blank">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel</a><br>
<br>
</blockquote></div><br>