Recent searches
No recent searches

Sergey
Joined Apr 16, 2021
·
Last activity Apr 16, 2024
Following
0
Follower
1
Total activity
39
Votes
6
Subscriptions
18
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Sergey
Sergey created an article,
Issue symptoms
I added RGB color elements to a help center article. However, after saving my draft and inspecting the source code, I see that the RGB has been replaced with HEX formatting.
The following is an example of RGB formatting:
After saving my changes, the RGB elements were replaced with the HEX format:
Resolution steps
The RGB color elements were converted to HEX formatting by TinyMCE, the WYSIWYG editor used for the content management of the help center. As a workaround, edit your articles to use RGBA instead, for example rgba(255, 99, 71, 0.5)
. RGBA elements do not automatically get converted into HEX.
For more information, see this article: How can I format the text of the article with the source code?
Edited Jun 10, 2024 · Sergey
0
Followers
1
Vote
0
Comments
Sergey commented,
0
Followers
0
Votes
0
Comments
Sergey commented,
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!
View comment · Posted Dec 14, 2022 · Sergey
0
Followers
1
Vote
0
Comments
Sergey commented,
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.
View comment · Posted Apr 25, 2022 · Sergey
0
Followers
0
Votes
0
Comments
Sergey commented,
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!
View comment · Posted Mar 10, 2022 · Sergey
0
Followers
0
Votes
0
Comments
Sergey commented,
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.
View comment · Posted Nov 17, 2021 · Sergey
0
Followers
0
Votes
0
Comments
Sergey commented,
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.
View comment · Posted Nov 05, 2021 · Sergey
0
Followers
0
Votes
0
Comments
Sergey commented,
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.
View comment · Posted Mar 19, 2021 · Sergey
0
Followers
0
Votes
0
Comments
Sergey commented,
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.
View comment · Posted Mar 09, 2021 · Sergey
0
Followers
0
Votes
0
Comments
Sergey commented,
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
View comment · Posted Feb 12, 2021 · Sergey
0
Followers
1
Vote
0
Comments