Ricerche recenti


Nessuna ricerca recente

Sergey's Avatar

Sergey

Data ingresso 16 apr 2021

·

Ultima attività 16 apr 2024

Zendesk Customer Care

Seguiti

0

Follower

1

Attività totali

39

Voti

6

Abbonamenti

18

PANORAMICA ATTIVITÀ

Ultima attività di Sergey

Sergey ha creato un articolo,

ArticoloAiuto su centro assistenza

Sintomi del problema

Ho aggiunto elementi di colore RGB a un articolo del centro assistenza. Tuttavia, dopo aver salvato la bozza e aver controllato il codice sorgente, ho notato che il formato RGB è stato sostituito con la formattazione HEX. 

Quello che segue è un esempio di formattazione RGB:
Codice sorgente.png

Dopo aver salvato le modifiche, gli elementi RGB sono stati sostituiti con il formato HEX:
Codice sorgente.png

Passaggi per la risoluzione del problema

Gli elementi di colore RGB sono stati convertiti in formattazione HEX da TinyMCE, l’editor WYSIWYG usato per la gestione dei contenuti del centro assistenza. Come soluzione alternativa, ad esempio, modifica gli articoli in modo da usare RGBA rgba(255, 99, 71, 0.5). Gli elementi RGBA non vengono convertiti automaticamente in formato esadecimale. 

Per ulteriori informazioni, leggi il seguente articolo: Come posso formattare il testo dell'articolo con il codice sorgente?

Avvertenza sulla traduzione: questo articolo è stato tradotto usando un software di traduzione automatizzata per fornire una comprensione di base del contenuto. È stato fatto tutto il possibile per fornire una traduzione accurata, tuttavia Zendesk non garantisce l'accuratezza della traduzione.

Per qualsiasi dubbio sull'accuratezza delle informazioni contenute nell'articolo tradotto, fai riferimento alla versione inglese dell'articolo come versione ufficiale.

Data ultima modifica: 26 giu 2024 · Sergey

0

Follower

1

Voto

0

Commenti


Sergey ha commentato,

CommentoManaging your email

That is correct!

Regards,
Serg

Visualizza commento · Data ultimo post: 14 dic 2022 · Sergey

0

Follower

0

Voti

0

Commenti


Sergey ha commentato,

CommentoManaging your email

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!

 

Visualizza commento · Data ultimo post: 14 dic 2022 · Sergey

0

Follower

1

Voto

0

Commenti


Sergey ha commentato,

CommentoMultiple language support

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.

 

Visualizza commento · Data ultimo post: 25 apr 2022 · Sergey

0

Follower

0

Voti

0

Commenti


Sergey ha commentato,

Commento nella community Developer - Zendesk APIs

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!

Visualizza commento · Data ultimo post: 10 mar 2022 · Sergey

0

Follower

0

Voti

0

Commenti


Sergey ha commentato,

CommentoUsing Built by Zendesk apps

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.

Visualizza commento · Data ultimo post: 17 nov 2021 · Sergey

0

Follower

0

Voti

0

Commenti


Sergey ha commentato,

CommentoSingle sign-on

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.

Visualizza commento · Data ultimo post: 05 nov 2021 · Sergey

0

Follower

0

Voti

0

Commenti


Sergey ha commentato,

Commento nella community Discussion - Tips and best practices from the community

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.

Visualizza commento · Data ultimo post: 19 mar 2021 · Sergey

0

Follower

0

Voti

0

Commenti


Sergey ha commentato,

Commento nella community Feedback - Ticketing system (Support)

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.

Visualizza commento · Data ultimo post: 09 mar 2021 · Sergey

0

Follower

0

Voti

0

Commenti


Sergey ha commentato,

CommentoSingle sign-on

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

Visualizza commento · Data ultimo post: 12 feb 2021 · Sergey

0

Follower

1

Voto

0

Commenti