最近の検索


最近の検索はありません

upbr ad's Avatar

upbr ad

参加日2022年12月30日

·

前回のアクティビティ2023年8月09日

フォロー中

0

フォロワー

0

合計アクティビティ

13

投票

0

受信登録

4

アクティビティの概要

さんの最近のアクティビティ upbr ad

upbr adさんが投稿を作成しました:

投稿 Developer - Zendesk Apps Framework (ZAF)

Hello,

Wondering if there is an API allowing to add/update message drafts in the Message Composer editor?  The Comments API posts a text as a public reply or private (internal note). However, before posting, the goal is to add/insert text into the editor for review by the agent.

Is there such an API, or ZAF client may support it?

投稿日時:2023年8月09日 · upbr ad

0

フォロワー

6

投票

4

コメント


upbr adさんがコメントを作成しました:

コメントTicket basics

Wondering if any of the APIs supports posting a comment or a response to a ticket using Draft mode? 

For example, one would expect Comments API has a Draft mode configuration, or this is added to anther API?
https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_comments/

 

Thank you,

コメントを表示 · 投稿日時:2023年8月08日 · upbr ad

0

フォロワー

0

投票

0

コメント


upbr adさんがコメントを作成しました:

コミュニティのコメント Developer - Zendesk Apps Framework (ZAF)

No, there is no instance IP restriction configured. 

Let me add that our code runs on a GCP (Google Cloud) VM and to the extent I know, there is no connection limitation from there.

コメントを表示 · 投稿日時:2023年7月16日 · upbr ad

0

フォロワー

0

投票

0

コメント


upbr adさんがコメントを作成しました:

コミュニティのコメント Developer - Zendesk Apps Framework (ZAF)

Hi Greg,

Appreciate your attention on this issue. I have passed the issue of "ZCLI Login" (using the unlock approach aboe). After successful login, and trying to build a package using the following command:

zcli apps:package dist

I get this error:

Error: Error: connect ECONNREFUSED ::1:443

Not sure what is wrong, as there is no extra step missing as per documentation, after login. Appreciate your help in pointing me to a direction where I can resolve this issue.

コメントを表示 · 投稿日時:2023年7月16日 · upbr ad

0

フォロワー

0

投票

0

コメント


upbr adさんがコメントを作成しました:

コミュニティのコメント Developer - Zendesk Apps Framework (ZAF)

An update on this case, I read somewhere that this could be due to locked keyring. The initial error is fixed and can login successfully after running the followings (to install dbus-11 as well): 

apt install dbus-x11 gnome-keyring 
export $(dbus-launch)
eval "$(echo '\n' | gnome-keyring-daemon --unlock)"

After successful login, I get the following error though on running any other command such as zcli apps:package {folder_name}:

Error: Error: connect ECONNREFUSED ::1:443

I logged out and ensure the subdomain is correct. Any idea of what else need to be done?

Thank you

 

 

 

 

 

 

 

 

 

コメントを表示 · 編集日時:2023年7月13日 · upbr ad

0

フォロワー

0

投票

0

コメント


upbr adさんがコメントを作成しました:

コミュニティのコメント Developer - Zendesk Apps Framework (ZAF)

Greg, thank you. I think I had done that before. Did and re-installed gnupg2 as you pointed out, and the issue is not resolved. Still getting:

Error: No such interface “org.freedesktop.Secret.Collection” on object at path /org/freedesktop/secrets/collection/login

コメントを表示 · 投稿日時:2023年7月13日 · upbr ad

0

フォロワー

0

投票

0

コメント


upbr adさんが投稿を作成しました:

投稿 Developer - Zendesk Apps Framework (ZAF)

Hello,

I have installed ZCLI on a GCP server, running Debian Unix OS. However, cannot login and get one of the following errors (in different terminals):

 Error: No such interface “org.freedesktop.Secret.Collection” on object at path /org/freedesktop/secrets/collection/login

or,

Error: Cannot autolaunch D-Bus without X11 $DISPLAY

 

Notes

1- I have gnome-keyring installed and seems that gnome-keyring-daemon is working.

2- In my account, API access with password and token is enabled.

 

Appreciate the help as I'm stuck.

投稿日時:2023年7月12日 · upbr ad

0

フォロワー

5

投票

6

コメント


upbr adさんがコメントを作成しました:

コミュニティのコメント Developer - Zendesk APIs

FYI, we switched to 2-step process where we get a code first, which comes as a parameter after '?' and then calling the token API to get the token which returns a JSON object. This solved the token request problem though the one-step token request parsing still remains unresolved.

コメントを表示 · 投稿日時:2022年12月31日 · upbr ad

0

フォロワー

0

投票

0

コメント


upbr adさんが投稿を作成しました:

投稿 Developer - Zendesk APIs

Hello,

As per Zendesk documentation for OAuth token (Using OAuth authentication with your application – Zendesk help), when requesting token directly, the token is included in the redirect URL as follows:

{redirect_url}#access_token=gErypPlm4dOVgGRvA1ZzMH5MQ3nLo8bo&token_type=bearer

When trying to get the token from the URL, in a Python-based backend with Flask request, the request object does not capture any argument from above because the hash fragment in the URL (anything after a '#' character) is not passed by the browser to the request object as it is the case with all parameters that follow standard '?'.

Anyone idea on how get the token from the URL when the callback function is a backend Python function, as opposed to a JS function?

To Zendesk development team: is there any reason that the standard '?' character is not used and instead '#' (hash fragments) are used to form this URL redirect?  

Thank you

編集日時:2022年12月31日 · upbr ad

0

フォロワー

3

投票

2

コメント