/build/static/layout/Breadcrumb_cap_w.png

Variable to use for name of Process Template?

I'm working on a KACE rule to send an email and would like to include the name of the Process Template in the message.  Here's what I *think* it should be (I've used HD_SERVICE.NAME to list Process Name in a Report), but it doesn't work in the rule:

select HD_TICKET.*,
                        HD_TICKET.ID AS TICKNUM,                                                  -- $ticknum
                        HD_TICKET.SUMMARY AS DESCRIPTION,                            -- $description
                        HD_SERVICE.NAME AS PROCESS_NAME,                             -- $process_name

............

 - The HD_SERVICE.NAME line causes my rule to fail.  If I leave it out, the rule has no errors.

If this worked, then I would use $process_name in the email message.


Thanks for any help you can provide.


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Hobbsy 1 month ago
Red Belt
0

It looks to me like you need to Join the HD_TICKET table to the HD_SERVICE table and the. You should be able to load the data value as a variable and use it in an email template. Feel free to get in touch if you want to work through this.

Posted by: Channeler 1 month ago
Red Belt
0

Here is the KACE SMA Administrator's guide.

https://support.quest.com/download/downloads?id=6116998

Page 265 and onwards, 'Tokens used in all email templates', lists all the wildcards\tokens available for emails.

These are only for email templates, I don't think they will work outside emails, e.g. custom ticket rules. (as they are pure SQL based).


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