Recent searches


No recent searches

Krsna Musterer's Avatar

Krsna Musterer

Joined Jan 31, 2024

·

Last activity Mar 20, 2024

Following

0

Followers

0

Total activity

6

Votes

2

Subscriptions

2

ACTIVITY OVERVIEW

Latest activity by Krsna Musterer

Krsna Musterer created a post,

Post Feedback - Admin Center

Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)

"Anybody can submit tickets" which is found at /admin/people/configuration/settings is a setting that is account-wide. However, it is desired that some forms are open to anyone, while others are only available behind the login.

What problem do you see this solving? (1-2 sentences) 

This change would allow us to actually use the web widget. 

We currently have all our forms behind a login. We now wish to add the web widget to one of our apps with only one form enabled. It seems it is not possible to use the web widget with "Anybody can submit tickets" disabled at /admin/people/configuration/settings. If we enable it, this setting stops requiring people to login before seeing our forms on our support site, which we absolutely don't want to change. This means our developers will need to find a different solution to allow users of this one product to submit tickets from within our app. Yet this is exactly what the web widget it supposed to do for us.
 
Because of this restriction, we are seeing this error in the console when we try to submit the form from the web widget: "Access to XMLHttpRequest at 'https://{OUR ZD DOMAIN}.zendesk.com/api/v2/requests' from origin 'https://www.{OUR APP WEBSITE}.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."
 
I could absolutely see this serving other purposes as well, sometimes there is a general enquiry form that should be open to everyone (maybe it goes to Sales), and a separate form for customers (that goes to Support). More control is always better.

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)

It took us over a week of investigation to understand why the web widget wasn't working. Finally a support agent asked me to enable that setting to make it work, which we won't do. So now we need to find a totally different way to allow people to submit tickets from within our app.

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

We will need to use a workaround, probably directing people to send an email, a completely new plan will be needed.

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

I'd like "Anybody can submit tickets" to be a setting on each form. I'd also like the information of this requirement to be somewhere more clear in documentation about the Web Widget, I didn't come across this requirement in any of my troubleshooting and searching support.zendesk.com.

Posted Feb 08, 2024 · Krsna Musterer

5

Followers

4

Votes

2

Comments


Krsna Musterer commented,

CommentWeb Widget (Classic) documentation

Hi there!

I'm trying to implement the Classic Web Widget. It's almost working, except that when I try to submit the contact us form it shows the following in the console:

"Access to XMLHttpRequest at 'http://{OUR SUBDOMAIN}.zendesk.com/api/v2/requests' from origin 'https://{DOMAIN WHERE I'M TRYING TO IMPLEMENT THE WIDGET}' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."

Not sure what I missed but I can't find anything here about this issue.
Help?

View comment · Posted Jan 31, 2024 · Krsna Musterer

0

Followers

0

Votes

0

Comments