How to filter a survey link based on ticket categorization?

Gary Snyder1
Tera Contributor

Hi Everyone!  We currently have surveys emailed to users after every ticket is closed/resolved.  The survey is a notification, based off the "Assessment" table, where it is triggered when the "Incident" is marked as "Resolved".  I'd like to filter this to prevent the survey from being sent to the user if the Category of the incident ticket is one particular value.  I've gone through the notification and the notification script which generates the HTML link and sends the email, but I cannot find how to relate the survey to the incident so I can say something along the lines of "If Category = NoSurvey, then do not send a survey".  The line of code (I'm assuming) would start something like "if trigger_table.category == "NoSurvey", but I don't see a dropdown to do this (hence the script requirement).

 

Any assistance you can provide is much appreciated.

 

Thanks in advance!

1 ACCEPTED SOLUTION

Nayan  Dhamane
Kilo Sage
Kilo Sage

Hello @Gary Snyder1 ,

Please follow the below steps to stop triggering survey for specific condition.

  1. Navigate to Survey > Trigger Conditions.
  2. Select the survey table which you want to edit.
  3. add the require condition. In your case category is not xyz.
  4. update the record.
If my answer solved your issue, please mark my answer as Correct & Helpful based on the Impact

Best Regards,
Nayan Dhamane
ServiceNow Community Rising Star 2023.

View solution in original post

2 REPLIES 2

Nayan  Dhamane
Kilo Sage
Kilo Sage

Hello @Gary Snyder1 ,

Please follow the below steps to stop triggering survey for specific condition.

  1. Navigate to Survey > Trigger Conditions.
  2. Select the survey table which you want to edit.
  3. add the require condition. In your case category is not xyz.
  4. update the record.
If my answer solved your issue, please mark my answer as Correct & Helpful based on the Impact

Best Regards,
Nayan Dhamane
ServiceNow Community Rising Star 2023.

Thank you!   I was looking in the wrong place!   And that explains why I didn't even see that it should be triggered when the ticket is resolved.  🙂