Paul Moran

I've added {{generative_answers}} to the search results template. I'd like to add tips to the top and bottom of the Quick Answers. I don't want to display the tips if Quick Answers doesn't show for a particular query. Also like to modify the font and other attributes of Quick Answers. I see the html code generated is in a shadow-root and that makes it difficult to update via javascript. Any tips on how to do it?

Yes, we have a similar need where we don't want certain sections of text to show up in the search results.

That tag sounds good, but failing that, at least a separate field that we could put stuff in, and it not being indexed.

We'd like to add an Internal Only section to some of the Articles but, currently, anything in that section of the article will also be indexed. 

Would be nice if there was a way of specify that certain text should not be indexed by Zendesk. Failing that, maybe another field on the article form that's not indexed by Zendesk. 

We currently use the Vue framework to help manipulate fields on our request form.

We just added a conditional field that shows/hides another field when you select a value. Alas, the condition doesn't work if I have the Vue code on the page. As soon as I remove the reference to Vue, it works.

There are no errors in the browser debug console. I'm guessing that Vue is somehow interfering with the listener events on the request form. 

Has anyone else had this kind of issue, or maybe someone can explain how the field event listeners work?

Hi, we've just created a new sandbox of our production instance. The production instance has legacy objects and I wanted to duplicate the setup by creating legacy objects in the sandbox, but I'm unable to do so because of the Sept 23 restriction. Is there any way of creating legacy objects, maybe using the api? We will migrate to the new objects, but it's going to take a while to do that!

Hi, it's still a problem. 

Allow a JWT token to be retrieved from /api/v2/help_center/integration/token even if you're not logged in. Then that token could be sent to the third party service which could verify it. Of course, the third party service couldn't verify the user, but at least it could verify the source of the call, ie that the call came from zendesk.

As for our use case, we use a third party service that provides additional functionality to our zendesk helpcenter pages, ie categories, sections and articles. We don't force users to log into our site so much of the time, this service is being called anonymously.

For more context on this JWT token feature: https://support.zendesk.com/hc/en-us/articles/5860358664730-Announcing-Secure-end-user-experience-integrations-for-Help-center#comment_5943682644890

I'm trying to use the unified search url below and I get a 403 error even though I'm logged into our zendesk hub:

/api/v2/guide/search?filter[locales]=en-us

If I try the article search /api/v2/help_center/articles/search, it works fine.

Is there a setting I'm missing?

Feature Request Summary: 

Zendesk Guide does not provide a way to render server-side Javascript on template pages. 

Description/Use Cases: 

We currently call third party apis that provide content on our template pages. To access those apis, we need an additional service layer. That service, which we've developed, would contain the authentication information used to access the third party services.  

Business impact of limitation or missing feature:

We currently have to develop add on solutions outside of Zendesk to help. We can't access third party apis directly, using client developed code.

Goal

Provide some way of doing server-side Javascript similar to NodeJS rendering would be so helpful! We could write server side javascript and process information from third party apis, all on the server-side, hidden from the client side browser.

I'd like to associate the external content with existing zd categories so that when you do a search 'By Category' the external content will show up in under that category's search results.

I can try to fudge it by using the associated external record's 'Type' or 'Source'. i.e. create a 'Type' record with the same name as the category i.e. a 'Widget A' category would have a 'Widget A' 'type' record. Not a great solution though.