[rt-users] onChangeToQueueXNotifyRequestors

[Myers, Adam]

Maybe 
  $self->TransactionObj->NewValue eq "3"
Should be:
  $self->TransactionObj->NewValue == 3


-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com
[mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Luke
Vanderfluit
Sent: Wednesday, March 01, 2006 3:42 PM
To: rt-users
Subject: [rt-users] onChangeToQueueXNotifyRequestors

Hi.

I'm struggling to get a scrip to work.

I want to notify the requestor when a ticket is changed from any queue
to queueA

I have the following:


Description:  onChangeToQueueXNotifyRequestors
Condition:    User Defined
Action:       Notify Requestors
Template:     Global template: Transaction
Stage:        TransactionCreate

Custom condition:
if (
      $self->TransactionObj->Type eq "Set"
 && $self->TransactionObj->Field eq "Queue"
 && $self->TransactionObj->NewValue eq "3"  # 3 is the number  for
queueA
 ) {
  return 1;
  } else {
  return 0;
  }

Custom action prep code:
Custom action cleanup code:

What should I change?
var/adm/messages shows:  'RT: error:    unexpected end of header\n\n 
(/usr/local/rt3/lib/RT/Template_Overlay.pm:369)'

Thanks.
Kind regards.

--
Luke

_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Download a free sample chapter of RT Essentials from O'Reilly Media at
http://rtbook.bestpractical.com

WE'RE COMING TO YOUR TOWN SOON - RT Training in Amsterdam, Boston and
San Francisco - Find out more at
http://bestpractical.com/services/training.html
* NOTE: This message is intended only for the use of the individual or entity to whom it is addressed and contains information that is privileged, confidential and exempt from disclosure. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately via reply e-mail and please delete this communication.