Recherches récentes
Pas de recherche récente

Sergey
Adhésion le 16 avr. 2021
·
Dernière activité le 16 avr. 2024
Suivis
0
Abonné
1
Activité totale
39
Votes
6
Abonnements
18
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 Sergey
Sergey a créé un article,
Symptômes
J’ai ajouté des éléments de couleur R Avec un article du centre d’aide. Cependant, après avoir enregistré mon brouillon et inspecté le code source, je vois que le formatage HTML a été remplacé par le formatage HEX.
Voici un exemple de formatage RGB :
Après avoir enregistré mes modifications, les éléments R importantes ont été remplacés par le format HEX :
Étapes de résolution
Les éléments de couleur R public ont été convertis au formatage HEX par tinyMCE, l’éditeur WYSIWYG utilisé pour la gestion du contenu du centre d’aide. Pour résoudre ce problème, modifiez vos articles pour qu’ils utilisent TextA, par exemple, rgba(255, 99, 71, 0.5)
. Les éléments SQLA ne sont pas automatiquement convertis au format HEX.
Pour en savoir plus, consultez cet article : Comment formater le texte de l’article via le code source ?
Traduction - exonération : cet article a été traduit par un logiciel de traduction automatisée pour permettre une compréhension élémentaire de son contenu. Des efforts raisonnables ont été faits pour fournir une traduction correcte, mais Zendesk ne garantit pas l’exactitude de la traduction.
Si vous avez des questions quant à l’exactitude des informations contenues dans l’article traduit, consultez la version anglaise de l’article, qui représente la version officielle.
Modification le 26 juin 2024 · Sergey
0
Abonnés
1
vote
0
Commentaire
Sergey a ajouté un commentaire,
That is correct!
Regards,
Serg
Afficher le commentaire · Publication le 14 déc. 2022 · Sergey
0
Abonnés
0
Votes
0
Commentaire
Sergey a ajouté un commentaire,
Hi James,
You can do so by putting "reject:" in front of users email address. See here for more info (just search for a "reject" keyword): https://support.zendesk.com/hc/en-us/articles/4408886840986-Using-the-allowlist-and-blocklist-to-control-access-to-Zendesk-Support
Give this a try!
Afficher le commentaire · Publication le 14 déc. 2022 · Sergey
0
Abonnés
1
vote
0
Commentaire
Sergey a ajouté un commentaire,
Hi François,
What will happen if you just enter "Español" as a 'name' attribute?
This is what I am seeing as a name for Spanish locale if I run an api call to list all locales: "/api/v2/locales.json"
If you are still stuck with this same question after trying above suggestion - try reaching out to support team, with your code handy.
Afficher le commentaire · Publication le 25 avr. 2022 · Sergey
0
Abonnés
0
Votes
0
Commentaire
Sergey a ajouté un commentaire,
Hi Chandrakant,
Albeit a bit too late - I hope that my answer will be helpful for any future developments on your side or for general public.
Password grant type is not supported by integrated chat accounts (your case) and is used on chat only accounts, as per Password grant type -
"This grant type is only supported on Chat-only accounts. It's not supported on Chat+Support accounts".
I can also see a 401 http response from our chat host for your attempts to get a token - it could indicate that your entered password/email do not match with login database. In case you are getting same error over and over - please reach out to our support team for further assistance, as there could be something unique to your account that prevents you from generating required token.
All the best!
Afficher le commentaire · Publication le 10 mars 2022 · Sergey
0
Abonnés
0
Votes
0
Commentaire
Sergey a ajouté un commentaire,
Hi Sam,
If it's still helpful - make sure you add groups and addresses in the following format (it is also mentioned above apps field, where you need to enter those values):
{ "Group_1": "group1@example.com", "Group_2": "group2@example.com", "Group_3": "group3@example.com" }
If you do, then there shouldn't be any errors thrown. If you are still seeing an error after syntax is checked - reach out to support.
Afficher le commentaire · Publication le 17 nov. 2021 · Sergey
0
Abonnés
0
Votes
0
Commentaire
Sergey a ajouté un commentaire,
Hi James,
Users in Zendesk are identified with email by default and email attribute is required when we talk about SSO authentication.
external_id will accept any values (numbers and characters) and you can pass this attribute in your SAML assertion payload (see above section of "Obtaining additional user data"), but it cannot be used as users primary identity.
Afficher le commentaire · Publication le 05 nov. 2021 · Sergey
0
Abonnés
0
Votes
0
Commentaire
Sergey a ajouté un commentaire,
Hu Bruno,
Wanted to share this handy article, that will demonstrate what you are after: https://develop.zendesk.com/hc/en-us/articles/360059146153#setting-custom-field-values
You can use this syntax, in particular:
{
"ticket": {
"subject": "Hello",
"comment": { "body": "Some question" },
"custom_fields": [{ "id": 34, "value": "I need help!" }]
}
}
Note, that if you will not pass Subject attribute/value combination at the time of creating a ticket, system will take some text from your Comment attribute and use that as a subject.
Afficher le commentaire · Publication le 19 mars 2021 · Sergey
0
Abonnés
0
Votes
0
Commentaire
Sergey a ajouté un commentaire,
There is nothing like it in Explore, I am sorry to say. Explore returns data based on datasets and those datasets are connected to objects/events, so unless object exists or an event has occurred - no data will be returned.
Explore can filter for user types, but only in regards to ticket requesters. If an agent has never been a requester of a ticket - you will not be able to get required data.
I would advise to use Search API to get the list of agents in JSON format (see here: https://developer.zendesk.com/rest_api/docs/support/search) and then you could utilise any tool available, that would convert JSON to CSV or Excel. There are plenty of free options available online.
Basic search query would look like this: subdomain.zendesk.com/api/v2/search.json?query=type:user%20role:agent
You can simply copy/paste it to your browser's address bar, adding your subdomain.
Afficher le commentaire · Publication le 09 mars 2021 · Sergey
0
Abonnés
0
Votes
0
Commentaire
Sergey a ajouté un commentaire,
Hi Derek,
It will mostly depend on SSO settings on IdP's side (is provisioning enabled or not, and if enabled - which values are pushed to Zendesk upon log on etc), but in general - no user can be deleted by SSO or any other auth. process.
SSO can do one/all of the following: demote/promote users (by passing role attribute in your xml payload) and change their name, organisations and so on.
Users will be synched at the most. At the least 0 simply allowed to enter your Help Center as is, without any changes to their profile/role/etc
Afficher le commentaire · Publication le 12 févr. 2021 · Sergey
0
Abonnés
1
vote
0
Commentaire