Re: [rt-users] Custom fields in transaction

2016-07-07 Thread Nilesh
For some reason I didn't see that option first when I wrote this message or it seemed to be absent. The problem is solved now, scrapped the idea of classifying by custom field and instead using regex to search inside subject & content. On Wed, Jul 6, 2016 at 5:56 PM, Jim Brandt

Re: [rt-users] Custom fields in transaction

2016-07-06 Thread Jim Brandt
Each scrip has a stage that is set as part of the configuration through the web UI. You should be able to find it on the Applies to tab when configuring the scrip. By default, it will be set to Normal. To get the scrip to run at the end in batch mode, you need to set that to Batch and save the

Re: [rt-users] Custom fields in transaction

2016-07-05 Thread Nilesh
The use case is simple, I want to move tickets to different queues based on a custom field and this should happen when the agent is replying. So transaction is the best place to introduce such a field. -- Nilesh On Tue, 2016-07-05 at 20:00 +0530, aniket tripathy wrote: > Hi Nilesh, > > Can

Re: [rt-users] Custom fields in transaction

2016-07-01 Thread Nilesh
Can you provide some example?  On the wiki I saw some scrip which was testing the return value of TransactionBatch method, but now after doing that I don't see the log.  In custom action commit code: my $batch = $self->TicketObj->TransactionBatch; if($batch) { RT::Logger->info("transaction

Re: [rt-users] Custom fields in transaction

2016-07-01 Thread Jim Brandt
On 6/30/16 11:41 PM, Nilesh wrote: Hi, I'm trying to assign the ticket to a queue based on a transaction custom field, but I am unable to fetch the custom field in my scrip. Scrip details: Condition: On correspond Action: User defined Template: Blank Custom condition: 1; Custom action

[rt-users] Custom fields in transaction

2016-06-30 Thread Nilesh
Hi, I'm trying to assign the ticket to a queue based on a transaction custom field, but I am unable to fetch the custom field in my scrip. Scrip details: Condition: On correspond Action: User defined Template: Blank Custom condition: 1; Custom action preparation code: 1; Custom action commit