Verne,
I always just do a “Reply” and make sure the only TO: address is RT.
Kenn
LBNLOn Thu, Oct 21, 2010 at 2:37 PM, Verne Baxter VerneB@team.sti.net wrote:
Kenneth, That worked! On the doco’s I found it showed
FirstCustomFieldValue(n) which I incorrectly took to signify a Number. I
know that the Scrips are numbered so thought there was some ‘hidden’ number
for each CustomField. Thank you. Uh, will this be sent to the group or
should I have did a Reply to All? I don’t use lists very often (that will
change!). Verne
From: Kenneth Crocker [mailto:kfcrocker@lbl.gov]
Sent: Thursday, October 21, 2010 2:26 PM
To: Verne Baxter
Subject: Re: [rt-users] Search Words for Custom Field Variable in Email
Verne,
You should try creating a template for that. Below is an example:
To: {$Ticket->FirstCustomFieldValue(‘QA Approver’)}@your suffix
Subject: Request Titled: “{$Ticket->Subject}” is ready to begin QA Testing!
TICKET INFORMATION:
Queue : {$Ticket->QueueObj->Name}
Number : {$Ticket->Id}
Subject: {$Ticket->Subject}
In this template, I’m overriding the “To:” but I am getting the info from a
Custom Field and then adding my suffix.
You’ll need to make changes to fit your situation. something like:
Dear {$Ticket->FirstCustomFieldValue(‘Full Name’)},
Bla bla bla.
Make sure there is one blank line between your “Subject” line and your
body.
Hope this helps.
Kenn
LBNL
On Thu, Oct 21, 2010 at 1:52 PM, Verne Baxter VerneB@team.sti.net wrote:
I have the feeling I’m searching using the wrong word(s). Please give me
the ‘buzz’ words to search this list for ‘how to write the code(?) in an
email that will be replaced by the contents of a Custom Field’. I have a
custom field ‘Full Name’ in my tickets. I wish the contents of that field to
be placed after ‘Dear’ in email correspondence (while I’m in the ticket) so
instead of Dear Subscriber (generic as heck) it will be Dear Wayne Glumpy.
‘mail merge’? ‘customfield variable’?
Verne Baxter
RT v3.8.2 on Fedora
This communication (including any attachments) contains information which
may be confidential and privileged. Unless you are the addressee (or
authorized to receive messages for the addressee), you may not use, copy or
disclose to anyone the message or any information contained in the
communication. If you have received the communication in error, please
advise the sender by reply e-mail and delete the communication. Nothing in
this communication should be interpreted as a digital or electronic
signature that can be used to authenticate a contract or other legal
document.
This communication (including any attachments) contains information which
may be confidential and privileged. Unless you are the addressee (or
authorized to receive messages for the addressee), you may not use, copy or
disclose to anyone the message or any information contained in the
communication. If you have received the communication in error, please
advise the sender by reply e-mail and delete the communication. Nothing in
this communication should be interpreted as a digital or electronic
signature that can be used to authenticate a contract or other legal
document.