[MOD] Adding Custom Fields To Email Body

[Ice Raider]

I finally got this software working and I love it , but I have been having some trouble with custom fields.

My question is how do you make custom fields show up in the body of the email message template for newticket.txt & newmessage.txt? We have a custom field that we are using that our help desk needs to change during the initial ticket submission and we want to make sure its communicated in all the email message that are sent out when ever the ticket is updated.

[Sparky]

Go to /setup.cgi to figure out which variable you want.  You'll need to know if it's c0, c1, c2, etc.

Simply add the macro into your email template...

(%c1%)

This assumes you're using the optional Layout Designer module.

[Ice Raider]

  Thanks but it didn't work, now when the email goes it out having a line with (%c0%) in the text, any thoughts?

Here is what is in my newticket.txt file looks like.

Dear (%UNAME%)

Thank you for contacting Nu-West Tech Solutions, this is an automated message to confirm that we have received you service request and someone will review it shortly.

Your ticket ID is: (%TICKETID%)

Estimated Solution Response Time: (%c0%)

--------------------Message Content--------------------------
(%MESSAGE%)
--------------------------------------------------------------------
You can review and update your service request by clicking the link below:

(%TICKETURL%)

Sincerely,

Nu-West Information Systems Tech Support

[Sparky]

Thanks but it didn't work, now when the email goes it out having a line with (%c0%) in the text, any thoughts?

Check over the email template very carefully for invisible characters or other formatting problems.

Even if that was an undefined or bad macro, TTX will ignore anything surrounded by these... (% %)

In other words, you should have seen any undefined/bad macros come through as blanks, you would never see the macro itself.

[Ice Raider]

Thanks for your help, I reviewed the formatting and decided to try putting an upper case "C" instead of a lower case "c" and it worked. 

[Sparky]

Hmm... flies in the face of the way the Perl module outputs that macro.

Glad it worked, anyway.

[Sparky]

Obviously my mistake.

I reviewed the Perl code again and must have misread the lower case "c" before.