最近搜索
没有最近搜索

Tanawat Oonwattana
已加入2021年4月15日
·
最后活动2024年2月07日
关注
0
关注者
0
活动总数
43
投票
9
订阅
14
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Tanawat Oonwattana
Tanawat Oonwattana 进行了评论,
Is this instruction outdated?
I think the setup is in role permission now.
查看评论 · 已于 2024年2月07日 发布 · Tanawat Oonwattana
0
关注者
0
投票
0
评论
Tanawat Oonwattana 进行了评论,
Hi,
When would this change be roll-out?
I am still not seeing 'Manage Team Member' ability in role permission page.
Thank you.
查看评论 · 已于 2023年9月18日 发布 · Tanawat Oonwattana
0
关注者
0
投票
0
评论
Tanawat Oonwattana 创建了一个帖子,
My company is trying to implement a new request list experience on Guide, however we have found bug that potentially prevent the change to be promoted to production.
When we enabled this beta experience, end-users are able to filter-up custom fields to be displayed on the column.
Let's say that I have a custom field, that is not visible for end-users below:
On the end-user's view in Guide, the user would still be able to query up this field:
Then the column will be displayed on the frontend, even the value of the fields are not actually being displayed (There are actually values in the field, but those are visible as blank for the end-users):
Ideally the fields that are not visible for the end-users should not be visible when selecting to 'show' or 'hide' the column.
Could someone having a look at this bug so that we could deploy the change without affecting the customer experience on September?
Thank you.
Tanawat
已于 2023年7月27日 编辑 · Tanawat Oonwattana
0
关注者
4
投票
3
评论
Tanawat Oonwattana 进行了评论,
Thanks for the update @...
I am also wondering if cursor based pagination is supporting ticket_events in incremental export?
From below doc, it says it only supports tickets/users, not ticket_events?
查看评论 · 已于 2023年5月30日 发布 · Tanawat Oonwattana
0
关注者
0
投票
0
评论
Tanawat Oonwattana 进行了评论,
Hi,
Thanks for the recommendation, but we will still be keeping with the Time based method.
The issue with cursor-based is that it gives out the next page path as code, e.g. https://{{subdomain}}.zendesk.com/api/v2/incremental/tickets/cursor.json?cursor=MTU3NjYxMzUzOS4wfHw0Njd8
This is making it very much difficult to troubleshooting in case of issues, or let's say that the service stops polling the ticket data, and want to restart the service, we would not know what was the time stamp that the service got stopped.
查看评论 · 已于 2023年5月30日 发布 · Tanawat Oonwattana
0
关注者
0
投票
0
评论
Tanawat Oonwattana 进行了评论,
Hi,
Do time based incremental export considered OBP or CBP? and does it get affected by this change?
查看评论 · 已于 2023年5月29日 发布 · Tanawat Oonwattana
0
关注者
0
投票
0
评论
Tanawat Oonwattana 进行了评论,
just a follow up on my question earlier, how soon will custom ticket staus be available with this new request list?
thakn you.
查看评论 · 已于 2023年5月16日 发布 · Tanawat Oonwattana
0
关注者
2
投票
0
评论
Tanawat Oonwattana 进行了评论,
Do you have the timeline to have Custom ticket status (CTS) available for this feature?
thanks.
查看评论 · 已于 2023年2月28日 发布 · Tanawat Oonwattana
0
关注者
1
投票
0
评论