최근 검색
최근 검색 없음

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
댓글