/build/static/layout/Breadcrumb_cap_w.png

Need a best practice for organizing a workflow

I've read and viewed all the tutorials on workflows. There is one particular detail that I did not see covered. In my workflow I'm going to have a software approval process. A user will request and then a decision board will approve and then it will move on to risk assessment and so on. Each ticket when closed kicks off the next one. But what if there is a denial along the way? For example, if the board denies the request. Is there an option to cancel the workflow and close that ticket without generating any subsequent tickets?

Thanks for the help.


2 Comments   [ + ] Show comments
  • For that level of sophistication you will have to do custom ticket rules. - Jbr32 10 years ago
    • Thanks JBR. I haven't actually run into that situation yet but it is sure to come up. I'll look in to that. - AndrewQ 10 years ago
  • A crazy problem that I'm having with this now is the Email notifications. I have it set up correctly for another queue so I copied that whole SQL and then just edited the email address. This new one will not send out an email. I have checked the syntax down to the letter.
    Is there something obvious or common that I may have overlooked with the email notifications that all the rookies do? This is making so little sense to me. It works fine for one but not the other. - AndrewQ 10 years ago
    • Is the rule enabled? - Jbr32 10 years ago

Answers (0)

Be the first to answer this question

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