Recherches récentes
Pas de recherche récente

Ivica Nedeljkovic
Adhésion le 25 mai 2022
·
Dernière activité le 18 févr. 2024
Suivis
0
Abonnés
0
Activité totale
8
Votes
0
Abonnements
4
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 Ivica Nedeljkovic
Ivica Nedeljkovic a créé une publication,
I have new custom object that should record some custom changes on tickets. I have ticket lookup relationship created on this custom object.
So what I would like when some change happen on ticket(for example when status of ticket is changed in most simple case), I would like to create new custom object of this type with link to ticket and some content.
How this can be done? Triggers doesn't have option to create new custom object records?
Only way I can think is to create webhook to some external system API, and that system could then create this custom object record via API. But I want to avoid using any external systems.
Publication le 18 févr. 2024 · Ivica Nedeljkovic
0
Abonnés
3
Votes
1
Commentaire
Ivica Nedeljkovic a créé une publication,
I created new custom object and created few records as admin via app. And as admin user I can view/update/search these records without issue from zendesk support app or via API(Postman).
I also set permissions for agents(check attachment), as described here:
https://support.zendesk.com/hc/en-us/articles/6034260247066-Configuring-agent-access-to-custom-object-records
However, if I try to list these custom objects, I can't, neither can view any of them via API and via zendesk support app I created. I get 403 forbidden error in both cases: "You do not have access to this page. Please contact the account owner of this help desk for further help." If I just switch to legacy objects, I can access them via API as agent.
Can someone confirm that custom objects can be accessed by agents, and what was processes of setting it apart of steps explained in article I shared.
Do I need to request some EAP feature?
Publication le 13 févr. 2024 · Ivica Nedeljkovic
0
Abonnés
3
Votes
0
Commentaire
Ivica Nedeljkovic a ajouté un commentaire,
I set permissions for staff(agents) to be able to view/edit custom objects, however, when I try to list/search or view records from this object type as agent(via zendesk support app), I get error code 403 forbidden with message: "You do not have access to this page. Please contact the account owner of this help desk for further help."
I also tested via API and get exactly same error.
I am sure that I set permissions correctly, and I can see correct permissions both on role page and also on custom object permissions page.
If I login as admin user, I can access these custom objects.
Do I need to set anything else? How long it take to propagate these permissions? And can you confirm that Agents can access custom objects at all(via API) after permissions are set correctly.
Update: This issue is resolved, the problem was that permissions propagation took more than 4 hours even in UI shows new permissions.
Afficher le commentaire · Modification le 18 févr. 2024 · Ivica Nedeljkovic
0
Abonnés
0
Votes
0
Commentaire
Ivica Nedeljkovic a créé une publication,
There are two methods available for revoking oauth tokens based on API documentation:
https://developer.zendesk.com/api-reference/ticketing/oauth/oauth_tokens/#revoke-token
However, we were able to revoke tokens only using first endpoint:
DELETE /api/v2/oauth/tokens/{oauth_token_id}
While revoking tokens using:
DELETE /api/v2/oauth/tokens/current.json
didn't work. Response we get in both cases were exactly same.
Also one additional thing we noticed is that if user generate one oauth token(go over oauth flow), and if after that user generate one more token, first token is not revoked, and it is not showing in UI.
So only after we revoke latest token, older one will appear in UI.
Not sure if this is desired behavior or bug(I think after new token is issued old one should become invalid).
Publication le 25 mai 2022 · Ivica Nedeljkovic
1
Abonné
2
Votes
1
Commentaire