
Chris Sos
-
Atividade total73
-
Última atividade
-
Membro desde
-
Seguindo0 usuário
-
Seguido por0 usuário
-
Votos7
-
Assinaturas34
Visão geral da atividade
Atividade mais recente por Chris Sos-
Chris Sos comentou,
Hi Gulcin, It sounds like you're running into a timeout error when trying to initialize the ngx-zendesk-webwidget in your Angular 11 web app. This can be a frustrating issue, but there are a few po...
-
Chris Sos comentou,
Comentário oficial Hi CJ, Thanks for your post. This article on our developer documentation may assist understanding the purpose of the signing secret: Verifying webhook authenticity The TL;DR is that this key is use...
-
Chris Sos comentou,
Hi Vladyslav, Thanks for your post. Just to note, multiple plans is still in beta and is not generally available. I've added your account to this beta so you should be able to select multiple plans...
-
Chris Sos comentou,
Hi Nathan, Nothing has been "taken away". ZAT is still fully supported as a Zendesk product until it is deprecated which will only happen once we have feature parity with ZCLI. This may be semantic...
-
Chris Sos comentou,
Hi CJ, Thanks for the question. So because apps are all effectively HTML, you would need to use HTML's line breaks (</br>) instead of JavaScript's \n character if displaying them within a paragraph...
-
Chris Sos comentou,
Hi Pulse, Dinesh is right in that there's no direct way to invoke a webhook. However, it's certainly possible to fire a webhook based on a trigger event. More details on how to do this are in this ...
-
Chris Sos comentou,
Hi Elizabeth Toy, That's correct. The webhooks will remain active regardless of the creating admin's status. Chris
-
Chris Sos comentou,
Hi there, If you're in support: client.get('currentUser') Is what you're looking for. This will return information on the user interacting with the app in Support. More details can be found here: h...
-
Chris Sos comentou,
Hi Gini, In Agent Workspace, CCs have moved to the public reply section instead of being grouped on the sidebar. See below: Hope this helps.
-
Chris Sos comentou,
Hi Michael, This error is usually caused by the proxy not being able to validate the certificate on the remote server and failing the request to ensure no credentials are leaked. I'll open a ticket...