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 you please explain,the use case. Just trying to understand the > scenario where a transaction custom field would be best fit. > > Thanks. > -Aniket > > On Fri, Jul 1, 2016 at 9:11 AM, Nilesh <[email protected]> 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 preparation code: > > 1; > > > > Custom action commit code: > > my $queueName = $self->TicketObj->QueueObj->Name; > > RT::Logger->info("Queue name: $queueName"); > > > > my $trans = $self->TransactionObj; > > RT::Logger->info($trans->FirstCustomFieldValue("Product")); > > > > ------------------ > > > > The method FirstCustomFieldValue returns empty even though the > > value is > > set in form submission. > > > > All the stuff I found on Google are about custom fields in tickets, > > seems nobody uses transaction custom fields? > > > > I'm using RT 4.4.0. > > > > -- > > Nilesh > > > > --------- > > RT 4.4 and RTIR Training Sessions https://bestpractical.com/trainin > > g > > * Los Angeles - September, 2016 > > --------- RT 4.4 and RTIR Training Sessions https://bestpractical.com/training * Los Angeles - September, 2016
