Gavin

Dane
I tried the method you linked here for using OR for multiple words, but it appears to be broken now with the new calculation restrictions on Explore.  Is there another method?

Ifra Saqlain

I have been able to hide a ticket from from the drop-down selector using the following code...

$(document).ready(function (){

  //Code for some specific ticket forms -- Start
  
  var tagsToRemove = ['16792736785805']; //special form ID
  
  function removeTagsWeDontWant() {
    $('.nesty-panel').on('DOMNodeInserted', function(e){
      for(var i in tagsToRemove) {
        $('li#' + tagsToRemove[i]).remove();
      }
    });
  };
removeTagsWeDontWant();

HOWEVER - this is now generating a "deprecated" error in the Chrome browser console...

jquery.min.js:2 [Violation] Listener added for a synchronous 'DOMNodeInserted' DOM Mutation Event.
This event type is deprecated (https://w3c.github.io/uievents/#legacy-event-types) and work is underway to remove it from this browser.
Usage of this event listener will cause performance issues today, and represents a risk of future incompatibility.
Consider using MutationObserver instead.

I see the recommendation is to use MutationObserver instead, however I'm not skilled enough to implement this on my own.  Do you have updated recommended code to hide a form?

Our Web Widget Classic presents the user with our ticket forms if they don't get an answer to their question.

I want the user to be logged in before web widget will let them submit their ticket via web widget.

If that's not possible, how can I have the web widget load for logged-in users, but not load for non-logged-in users?  Or even better, take them through the login flow before they can submit their ticket?

We already know how to make our Submit a Request button do this - logged-in users are taken directly to the web form, non-logged-in users are taken through our login flow before being taken to the web form.  We want the same thing to happen with the Web Widget.

Thanks Ifra Saqlain

Does this go into the script.js file?

What if we want to do the inverse?  We have about a dozen forms, and only want to hide one or two of them.  Is there a way to say "hide these forms" instead of "show these forms"?

Hello.

I successfully used these instructions to remove my form from the form-selection-list.

https://support.zendesk.com/hc/en-us/community/posts/4409217680410/comments/4409692632474

However the form still appears in the Web Widget as a selectable form.  How can I remove it from the Web Widget, also?

Hi.  I want to block rendering the form selection field on one specific form only.

Example -

I have three ticket forms - A, B, and C.  I have already figured out how to hide form C from the drop-down list, so now the only way to access form C is via a link.  So far so good.  However once form C loads, I would like to block the form selection field from rendering on form C.  So the outcome is, you can only get to form C via a link, and when form C loads, you cannot select a different form.  However forms A and B should continue to render the form selection field.

How can I accomplish this?

Max McCal FWIW, we're trying to achieve the exact same thing as Serge Pincon.

The goal is to eliminate spam, reduce the need for ticket merges, and have users authenticated right from the very beginning of the ticket (which reduces touches).  So most of the forms should require authentication.  But then a select one or two forms (lost password and legal) should be open for unauthenticated users to fill out.

Accomplishing this should also not break the Web Widget Classic.

Hi Orsolya Forster Joel Sandi

I'm also in need of the ability to count published articles per month and see that growth over time.  Not the publishing event - but the actual count of total articles available on our help center.  Did you ever come up with a solution for this?  So far all my attempts have resulted in a count of publishing events.

Janel

We have found that the filter "learns" as long as we ongoingly have someone review the suspended tickets queue.  So a couple weeks of un-suspending tickets that should not have been suspended trains the filter over time, and false-positives drop.

In our experience, you have to continue to review the queue over time.  You cannot simply get it to "good enough" and then stop reviewing.  The filter will lose training and at the same time, spammers tactics change.

We don't have any custom apps creating tickets, and yet we see "via system" on many tickets.  What could be causing this?  I've submitted a support ticket, but surely we're not the only ones experiencing this.