Eric Norris

We got an updated script that seems to work. Not sure how, and there might be a more elegant way of writing it, but it seems to work. Hope this helps:

  var tagsToRemove = ['thing_1','thing_2','thing_3'];
 removeTagsWeDontWant();
 
 function removeTagsWeDontWant()
 {
   const removeNodes = (node) => {
     for (let i = 0; i < node.childNodes.length; i++) {
       const wasRemoved = removeNodes(node.childNodes[i]);
       if (wasRemoved) {
         i--;
       }
     }

     if (node.nodeType === 1 && tagsToRemove.includes(node.getAttribute("id"))) {
       node.parentNode.removeChild(node);
       return true;
     }
     return false;
   };

   const observer = new MutationObserver(mutationList =>
     mutationList.filter(m => m.type === 'childList').forEach(m => {
       m.addedNodes.forEach(removeNodes); 
     }));  
   document.querySelectorAll('.nesty-panel').forEach(panel => observer.observe(panel,{childList: true, subtree: true}));
 }

Hi Ifra,

I've used your original code for some time now and it worked great. For some reason, today it stopped working in Chrome. Not sure why this is happening as the only changes we made were to add tags as we go, and haven't done that in recent memory. Do you have any ideas? Thanks
Code using for reference:

$(document).ready(function() 
{
 var tagsToRemove = ['XXXXXX','YYYYYY'];
 removeTagsWeDontWant();
 
 function removeTagsWeDontWant() 
 {
   $('.nesty-panel').on('DOMNodeInserted', function(e)
   {
     for(var i in tagsToRemove) 
     {
       $('li#' + tagsToRemove[i]).remove();
     }
   });
 }

Hello,

When looking at Zendesk API usage (APIs -> Zendesk API -> Activity), I see an average rate usually around the mid teens. When I look at the graph though, it seems like the spikes are in the 200-250 range. I do have the High Volume API because we were expecting some significant API usage, but that hasn't materialized. 

I would like the ability to export the hourly rate of API usage over as much time as possible; 2 weeks at least, 90 days would be ideal. 

Thanks.

Hello,

We are doing an exercise in removing and consolidating triggers. We have 315 triggers, and may be able to get them down to just over 200. However, there is no easy way to get the list of triggers we actually have, so this has become a slower process than anticipated.

I would like to see a way to export the list of triggers that are currently active that does not require creating an API. I would like to be able to export a csv file that includes trigger name, category, description and last 7 days of activity. Bonus points if we can chose our own time frame of activity (7 days/14 days/30 days and/or choose date(s)). Extra bonus points if we can also choose active and/or deactivated triggers.

Thanks.

Hello,
We are getting crashes when using the Zendesk UNIFIED SDK IOS version (Objective-c). After we open and close the Help Center a few times our app crashes with memory warnings. I believe it is an out of memory issue. I would like to know the best way to release (deallocate) memory right after I close the Help Center Screen.
Is this memory issue a known error? Can we have more control over the ticket creation screen and the Help Center screen?

Hello,

My localization team has an API that it uses to POST and PUT translations for our knowledge base articles. However, when we try to do that with articles that have content blocks, we are seeing that those articles appear blank if we go to edit them. It seems that when the localization team goes to GET the body of the article, the content blocks are not going with it. Is there an API call available where we can get the content blocks in with the article? If not, is there any other solution for automating content block translations?
Thanks.

Hi Stephen,

I do find that interesting. I am curious what metrics you use to be able to do that type of reporting.

Thanks!

Hello,

Sometimes when we want to do a deep dive into a particular issue, we'll use phrases used by either the customer or by our agents to bring up tickets in the Support Search. It would be something along the lines of:
"lorem Ipsum" order_by:created_at sort:desc

Since Explore does not allow us to use the Description textarea field, It would be helpful and efficient if we could export these results right from the search results. If we were able to get a CSV, we could use that in Excel or import that into Looker so we can do out deep dive.

Thanks

Hello,

Looking at the knew Knowledge and Search dashboard, and I was unable to find a filter for Category. Each of our products has its own category, and various help sections underneath. It would help us to understand the health of our KB articles if we had a per product view using category.

Thanks.

Hello,

I was looking for an Explore solution for finding the percentage of customers who go to an article that did not submit a ticket shortly thereafter. Looking at the dashboard that came out about 3 weeks ago and checking on metrics, I did not see a way to do this. I do see a way to do that via Google Analytics, but would rather have it within Explore so we can centralize our reports there, as well as reduce the effort of needing to grab data from across various data points.

Thanks.