[rt-users] Scrip access to Per-Transaction custom field values -- need a workaround !!

[Al Joslin]

Alex, 

	Thank you so much, that worked wonderfully !!

	I updated the wiki page to say:

Note that Per-Transaction custom fields values are not available to ScripActions, (RT sets these after the Scrip has been executed) unless you change the Global Scrip Stage from Normal to Batch in the Applies to Page for your Scrip (as described in TransactionBatchStage .)  If your Scrip is set to Batch then it will be run after all the Transactions have been created.

	Thanks again,
Al;

On Jul 30, 2014, at 8:40 PM, Alex Peters <alex at peters.net> wrote:

> I wonder whether that note on the wiki page still applies to scrips that run in batch mode, where the scrip runs after all transactions complete.
> 
> Consider trying a batch scrip (which has multiple transactions available to it).  A batch scrip can look at all the transactions and hopefully find the custom fields at that point.
> 
> If it does work for you, the community would probably appreciate you updating that wiki text as well.
> 
> On 31/07/2014 6:29 am, "Al Joslin" <allen.joslin at gmail.com> wrote:
> I have per-transaction custom fields that the users can update when they comment (or reply) 
> 
> I need to roll those up to the Ticket as they are added, so I wrote a scrip
> 
> But I can't seem to get it to work...  It's always one comment behind...
> 
> Then I found this line in the RT wiki 
> 
> 	Quote:     Note that Per-Transaction custom fields values are not available to ScripActions. (RT sets these after the Scrip has been executed.)
> 	from:    http://requesttracker.wikia.com/wiki/ScripAction
> 
> Damn, that means my displayed roll-up in the Ticket will forever be inaccurate...
> 
> Are there any suggested work-arounds?
> 
> thanks
> al;
> 
> 
> 
> --
> RT Training - Boston, September 9-10
> http://bestpractical.com/training

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20140731/1c6e878f/attachment.htm>