/build/static/layout/Breadcrumb_cap_w.png

Kace Rules

My company is just moving into the Kace environment and I've been put into setting some rules on Kace.

I am sorta familiar with MySQL, but dont understand the naming convention for Kace.

I need to set a rule where a user cannot submit a ticket with  a category of (Select) and send an error if they do. I've tried the wizzard to set this rule but it does not work.

3 Comments   [ + ] Show comments
  • Rules don't take place until after the ticket is saved so we can't prevent the user from opening the ticket.

    You can create a rule that would then close the ticket and send custom email that indicates they didn't select a category and to create a new ticket. - nshah 9 years ago
  • Can you make the category a required field? - tshupp 9 years ago
    • You can make the category required but you can't have a category of blank as the default. So we currently have as please select... as a default category. But I'm trying to figure out if there is a wat to write a rule to check that if the category is equal to please select then I would prompt user to change that or to send them an email stating they have imputed an invalid category. I have the rule to email them if the category is the default but It still creates the ticket. I'm not sure how to close the ticket if it has the parameters of the default value. Like I said I'm new to MySQL and trying to figure out what are the public keys and what table interest with each other is probing to he difficult.

      The goal is to not have tickets opened of the category us set to 'please select...' that's my trouble. - shadowtype09 9 years ago
  • Did you ever find a solution for this? Thanks - kshea 8 years ago

Answers (0)

Be the first to answer this question

 
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