/build/static/layout/Breadcrumb_cap_w.png

Accessing Custom Fields in Ticket Rule

I've created a custom ticket rule to notify the owner when a ticket is overdue by sending an email. That part works great. Now what I want to do is make the email a little more informative. I am able to include things like category, impact, priority, submitter, etc... but I also want to include information from a custom field in the ticket layout. (I have defined CUSTOM_1 as a single select field with about 30 different possible string values. I want to display the chosen string value)
Reading through posts and KB articles, I came across something that said in order to access the custom field data I need to use the appropriate column, CUSTOM_FIELD_VALUE0,1,2 etc... So, how exactly do I use that within my ticket rule? What do I put it in the query and where do I put it? Also, am I correct in assuming that these CUSTOM_FIELD_VALUE0 corresponds to CUSTOM_1 in the ticket layout?
Any help is appreciated, thanks.

0 Comments   [ + ] Show comments

Answers (1)

Posted by: GillySpy 13 years ago
7th Degree Black Belt
0
You would add CUSTOM_FIELD_VALUE0 in your query.
e.g.

select CUSTOM_FIELD_VALUE0, ...


In your email you would reference it as $custom_field_value0

This might help too:
http://www.kace.com/support/kb/index.php?action=artikel&cat=8&id=965&artlang=en#Overview_of_Email_choices

Also the bubble help in a rule editor explains this
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ