最近搜索
没有最近搜索

Sergey
已加入2021年4月16日
·
最后活动2024年4月16日
关注
0
关注者
1
活动总数
39
投票
6
订阅
18
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Sergey
Sergey 创建了一篇文章,
问题特征
我在一篇帮助中心文章中添加了RGB 颜色元素。然而,在保存草稿并检查源代码后,我发现RGB已被十六进制格式替换。
以下是 LED 格式的示例:
保存更改后,RGB 元素将替换为 HEX 格式:
解决步骤
其中,RGB 颜色元素已由TinyMCE(用于帮助中心内容管理的所见即所得编辑器)转换为十六进制格式。解决方法是编辑您的文章以使用RGBA,例如 rgba(255, 99, 71, 0.5)
更新。GBA 元素不会自动转换为 HEX。
有关更多信息,请参阅文章:如何使用源代码设置文章的文本格式?
翻译免责声明:本文章使用自动翻译软件翻译,以便您了解基本内容。 我们已采取合理措施提供准确翻译,但不保证翻译准确性
如对翻译准确性有任何疑问,请以文章的英语版本为准。
已于 2024年6月26日 编辑 · Sergey
0
关注者
1
投票
0
评论
Sergey 进行了评论,
0
关注者
0
投票
0
评论
Sergey 进行了评论,
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!
查看评论 · 已于 2022年12月14日 发布 · Sergey
0
关注者
1
投票
0
评论
Sergey 进行了评论,
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.
查看评论 · 已于 2022年4月25日 发布 · Sergey
0
关注者
0
投票
0
评论
Sergey 进行了评论,
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!
查看评论 · 已于 2022年3月10日 发布 · Sergey
0
关注者
0
投票
0
评论
Sergey 进行了评论,
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.
查看评论 · 已于 2021年11月17日 发布 · Sergey
0
关注者
0
投票
0
评论
Sergey 进行了评论,
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.
查看评论 · 已于 2021年11月05日 发布 · Sergey
0
关注者
0
投票
0
评论
Sergey 进行了评论,
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.
查看评论 · 已于 2021年3月19日 发布 · Sergey
0
关注者
0
投票
0
评论
Sergey 进行了评论,
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.
查看评论 · 已于 2021年3月09日 发布 · Sergey
0
关注者
0
投票
0
评论
Sergey 进行了评论,
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
查看评论 · 已于 2021年2月12日 发布 · Sergey
0
关注者
1
投票
0
评论