Recherches récentes
Pas de recherche récente

Jonathan Farache
Adhésion le 03 janv. 2022
·
Dernière activité le 21 mars 2023
Suivis
0
Abonnés
0
Activité totale
8
Votes
0
Abonnements
3
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Jonathan Farache
Jonathan Farache a ajouté un commentaire,
Anne Ronalter is there a resource that goes over migration between the different API clients?
With live chat we had the zE object to show/hide the chat widget as well as listen/respond to certain events. What's the equivalent in zendesk messaging? What's the best practice for migrating from one to the other?
Afficher le commentaire · Publication le 21 mars 2023 · Jonathan Farache
0
Abonnés
0
Votes
0
Commentaire
Jonathan Farache a ajouté un commentaire,
can we see an example of how this works with the `zE("...")` API?
unclear from the docs here how to send structured messages with zE
Afficher le commentaire · Publication le 16 août 2022 · Jonathan Farache
0
Abonnés
0
Votes
0
Commentaire
Jonathan Farache a ajouté un commentaire,
Thanks for the reply Eric Nelson
I should have clarified: we already have a webhook setup. It sends data to an AWS SQS, and from there our app grabs each message as it comes in. The problem is that sometimes AWS goes down, and then we lose some data until it's back up. In those instances, I need to re-sync my data.
You might say "well why don't you connect the webhook directly to the app" - that's not possible for both security reasons, but also the fact that the app itself might go down and then we're in the same issue - hence the need to occasionally re-sync.
Afficher le commentaire · Modification le 05 janv. 2022 · Jonathan Farache
0
Abonnés
0
Votes
0
Commentaire
Jonathan Farache a ajouté un commentaire,
yes Eric Nelson, i was thinking of implementing a process that runs every 5 minutes and validates the the tickets in my DB from the last hour are synced with tickets in ZD. That would easily be hundreds of tickets every 5 minutes
but with this amount of network traffic it seams unfeasible
Afficher le commentaire · Publication le 04 janv. 2022 · Jonathan Farache
0
Abonnés
0
Votes
0
Commentaire
Jonathan Farache a créé une publication,
Currently when you make a request for ticket data, you get all the data for that ticket back. So if I asked for data about 100 tickets, I could potentially get 100,000 lines of JSON because it includes all the custom_fields (which can be a lot per ticket) - this is a huge amount of data to return (i.e. useless network traffic) for 100 tickets when all I want is the ticket status and priority for each ticket.
I was advised by customer support that such a feature does not exist - could we make this happen?
Publication le 03 janv. 2022 · Jonathan Farache
1
Abonné
4
Votes
7
Commentaires