Recherches récentes


Pas de recherche récente

Jean-Charles Pascale's Avatar

Jean-Charles Pascale

Adhésion le 16 avr. 2021

·

Dernière activité le 13 févr. 2025

Suivis

0

Abonné

1

Activité totale

46

Votes

7

Abonnements

11

APERÇU DES ACTIVITÉS

Dernière activité effectuée par Jean-Charles Pascale

Jean-Charles Pascale a ajouté un commentaire,

Commentaire de la communauté Français Communauté
Bonjour Denis,

D'après notre documentation, votre bundle devrait contenir un Job Spec (https://developer.zendesk.com/documentation/integration-services/zis-tutorials/getting-started/building-your-first-zis-integration/#defining-a-zis-job-spec).
Celui-ci devrait contenir les détails de l'event qui devrait trigger un flow. Ces détails devraient être les attribute event_source et event_type dans l'exemple ci-dessus.
Vous pouvez trouver la liste des events disponibles ici: https://developer.zendesk.com/api-reference/integration-services/trigger-events/introduction/
Je pense que vous serez interessé par celui-là: Custom Field Changed : https://developer.zendesk.com/api-reference/integration-services/trigger-events/ticket-events/#custom-field-changed
Notez que cet event est particulier, et vous devrez donc ajouter un object "custom_field" pour y ajouter l'ID du field entre autres, commes décrit dans la documentation ci-dessus.

 

Afficher le commentaire · Publication le 23 oct. 2023 · Jean-Charles Pascale

0

Abonnés

0

Votes

0

Commentaire


Jean-Charles Pascale a ajouté un commentaire,

CommentaireUsing the knowledge base in Help Center
Hi Rich,
The feature is being looked into, but it is not available at the moment.
I would recommend checking this post (https://support.zendesk.com/hc/en-us/community/posts/4409222532506/comments/4409239462810) and page and vote for this feature to show interest in it.
 

Afficher le commentaire · Publication le 17 oct. 2023 · Jean-Charles Pascale

0

Abonnés

0

Votes

0

Commentaire


Jean-Charles Pascale a ajouté un commentaire,

CommentaireAttachments and CCs

Hi Eune,

The only way I can think of would be to use the Ticket Skips API to fetch the tickets skipped for specific agents, and display them either in a Sidebar App in Zendesk, or outside of Zendesk.
However, this is not a native feature of Zendesk and will require some custom technical implementation.

-JC

Afficher le commentaire · Publication le 08 mars 2022 · Jean-Charles Pascale

0

Abonnés

0

Votes

0

Commentaire


Jean-Charles Pascale a ajouté un commentaire,

CommentaireAttachments and CCs

Hi Eune,

According to my tests, it seems like this is only available to Administrators and the agents themselves. However, the Team Lead was not able to see the tab.

-JC

 

Afficher le commentaire · Publication le 07 mars 2022 · Jean-Charles Pascale

0

Abonnés

0

Votes

0

Commentaire


Jean-Charles Pascale a ajouté un commentaire,

CommentaireAttachments and CCs

Hi Eune,

The playlist will not have any limit based on time for the results it displays. However, since this is fetching the skips from our API, Archived tickets will not be included.
I hope this clarifies the behavior of the feature.

-JC

Afficher le commentaire · Publication le 03 mars 2022 · Jean-Charles Pascale

0

Abonnés

0

Votes

0

Commentaire


Jean-Charles Pascale a ajouté un commentaire,

CommentaireUsing Built by Zendesk apps

Hi William,

If I understand correctly, you have a field that is hidden for light agents, but that is also set as "mandatory" for your agents to fill in, therefore preventing your light agents from submitting any changes to the ticket if the field is empty?

Does this field need to be mandatory/hidden from the light agents?

The main workaround here that I could see would be to add a warning when a mandatory field is hidden, as we cannot override the field being set as "hidden".

-JC

Afficher le commentaire · Publication le 28 févr. 2022 · Jean-Charles Pascale

0

Abonnés

0

Votes

0

Commentaire


Jean-Charles Pascale a ajouté un commentaire,

CommentaireHow to manage the help center
Hi Mohit,
 
Indeed, at the moment, to display an article to the end user using the Flow Builder, the article cannot be restricted to signed-in users.
As per a restriction on articles by still keeping them "Visible to Everyone", it should be possible via Custom code, but I do not have any template/example that I can provide for this.
I just know that they used the HelpCenter.user JavaScript object to detect if the user was logged in or not, like in this example to detect the organization of a user to hide some ticket fields in the form.
 
Hope this helps,
 
-JC

Afficher le commentaire · Publication le 31 déc. 2021 · Jean-Charles Pascale

0

Abonnés

0

Votes

0

Commentaire


Jean-Charles Pascale a ajouté un commentaire,

Commentaire de la communauté Feedback - Ticketing system (Support)

Hi Louis,

If you simply set a macro to set the title, then it should work immediately in the ticket indeed.

I attempted with a macro that sets the subject to {{ticket.title}} [{{ticket.organization.custom_fields.champ_org_dropdown}}] and it works as expected.

Could you confirm that the issue happens in any browser and in incognito mode?

Could you confirm that the issue also happens without the apps on your account? You can temporarily disable them for your session using ?noapps, as described in our documentation

-JC

Afficher le commentaire · Publication le 10 nov. 2021 · Jean-Charles Pascale

0

Abonnés

0

Votes

0

Commentaire


Jean-Charles Pascale a ajouté un commentaire,

Commentaire de la communauté Feedback - Ticketing system (Support)
Hi Louis,
 
When doing a similar test via APi, indeed, the placeholders are not replaced. Like I mentioned, even though in the API call you set the fields to a specific value, when the ticket creation in processed, those values do not exist yet in the ticket, and the placeholder therefore has no value.
However, when you submit the ticket again, the value is now there and the value is therefore replaced in the subject.

Afficher le commentaire · Publication le 05 nov. 2021 · Jean-Charles Pascale

0

Abonnés

0

Votes

0

Commentaire


Jean-Charles Pascale a ajouté un commentaire,

Commentaire de la communauté Feedback - Ticketing system (Support)
Hi Louis,
 
If I understand correctly, the correct data is populated on the second submission of the subject of the ticket.
If so, this is an expected behavior. Indeed, at ticket creation time, the organization of the ticket is not defined, and therefore the placeholder for ticket.organization.XXXXX has no real value. The placeholder is therefore not replaced.
 
When you update the ticket a second time, the ticket has a set organization, and therefore the placeholder has a set value and is replaced when the ticket is submitted again.
 
I hope this clarifies the behavior of the placeholders.
Kind Regards,

Afficher le commentaire · Publication le 03 nov. 2021 · Jean-Charles Pascale

0

Abonnés

0

Votes

0

Commentaire