Tanawat Oonwattana
-
총 활동 수43
-
마지막 활동
-
회원 가입일
-
내가 팔로우하는 사용자 수0명
-
나를 팔로우하는 사용자 수0명
-
투표 수9
-
플랜 수13
활동 개요
Tanawat Oonwattana님의 최근 활동-
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.
-
Tanawat Oonwattana님이 에 댓글을 입력함
+1 this post has been flowing for 2 years, why this feature has not been implemented yet?
-
Tanawat Oonwattana님이 에 댓글을 입력함
Hi Spencer, This is actually true, tried incognito with the actual signing in with end-user's id/pw and do not see the fields, thanks for the recommendation!
-
Tanawat Oonwattana님이 에 게시물을 만듦
Bug on new request list experience (Beta)
답변함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 exper...
-
Tanawat Oonwattana님이 에 댓글을 입력함
Thanks for the update Sanjeev Mandalapu I am also wondering if cursor based pagination is supporting ticket_events in incremental export? https://developer.zendesk.com/api-reference/ticketing/ticke...
-
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}}.z...
-
Tanawat Oonwattana님이 에 댓글을 입력함
Hi, Do time based incremental export considered OBP or CBP? and does it get affected by this change? reference: https://developer.zendesk.com/documentation/ticketing/managing-tickets/using-the-incr...
-
Tanawat Oonwattana님이 에 댓글을 입력함
Hi Gorka Cardona-Lauridsen, just a follow up on my question earlier, how soon will custom ticket staus be available with this new request list? thakn you.
-
Tanawat Oonwattana님이 에 댓글을 입력함
Do you have the timeline to have Custom ticket status (CTS) available for this feature? thanks.
-
Tanawat Oonwattana님이 에 댓글을 입력함
Hi Christine, I might not explain this clearly for you, apology for that. for example, there was a ticket ID #1 and it got closed by one of the agent, then the customer sent another email on top of...