/build/static/layout/Breadcrumb_cap_w.png

manually generate ticket email via database insertion

Hello,

Does anyone know how to trigger an email action from manually inserting a comment row in a ticket DB? I have the sql all set to insert the custom comment, and it works. Playing with the other HD_TICKET_CHANGE fields, I cant seem to get it to trigger an email to go out to the ticket recipients. 

Best, Tim

0 Comments   [ + ] Show comments

Answers (1)

Posted by: chucksteel 8 years ago
Red Belt
1
Rules are triggered either by a ticket being saved or on a scheduled basis. For rules that run on ticket save manually inserting into the database won't trigger the rule to run. 

Comments:
  • thanks Chuck, so the process that sends an email out to a recipient is only triggered on ticket save? So if I have a rule that runs once a day, inserting a column, its never going to trip the 'ticket was saved' ? - tholmes 8 years ago
    • If a rule is set to run on a schedule then it will still run based on those settings (daily, hourly, etc,). Rules don't generally trip the 'ticket was saved' option, as far as I know. You can have a rule that adds a comment using that checkbox in the rule configuration, and that should trigger a rule that runs on tickets being saved. - chucksteel 8 years ago
      • yup, in this particular rule, I'm inserting a custom comment, directly into the ticket change DB, to get around the inability to add custom variables to the built in ticket comment box. And to also use the HTML email features outside the ticket rules. - tholmes 8 years ago

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