最近の検索
最近の検索はありません
Jean-Charles Pascale
参加日2021年4月16日
·
前回のアクティビティ2025年2月13日
フォロー中
0
フォロワー
1
合計アクティビティ
46
投票
7
受信登録
11
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Jean-Charles Pascale
Jean-Charles Pascaleさんがコメントを作成しました:
D'après notre documentation, votre bundle devrait contenir un Job Spec (https://developer.zendesk.com/documentation/integration-services/zis-tutorials/getting-started/building-your-first-zis-integration/#defining-a-zis-job-spec).
Celui-ci devrait contenir les détails de l'event qui devrait trigger un flow. Ces détails devraient être les attribute event_source et event_type dans l'exemple ci-dessus.
Vous pouvez trouver la liste des events disponibles ici: https://developer.zendesk.com/api-reference/integration-services/trigger-events/introduction/
Je pense que vous serez interessé par celui-là: Custom Field Changed : https://developer.zendesk.com/api-reference/integration-services/trigger-events/ticket-events/#custom-field-changed
Notez que cet event est particulier, et vous devrez donc ajouter un object "custom_field" pour y ajouter l'ID du field entre autres, commes décrit dans la documentation ci-dessus.
コメントを表示 · 投稿日時：2023年10月23日 · Jean-Charles Pascale
0
フォロワー
0
投票
0
コメント
Jean-Charles Pascaleさんがコメントを作成しました:
The feature is being looked into, but it is not available at the moment.
I would recommend checking this post (https://support.zendesk.com/hc/en-us/community/posts/4409222532506/comments/4409239462810) and page and vote for this feature to show interest in it.
コメントを表示 · 投稿日時：2023年10月17日 · Jean-Charles Pascale
0
フォロワー
0
投票
0
コメント
Jean-Charles Pascaleさんがコメントを作成しました:
Hi Eune,
The only way I can think of would be to use the Ticket Skips API to fetch the tickets skipped for specific agents, and display them either in a Sidebar App in Zendesk, or outside of Zendesk.
However, this is not a native feature of Zendesk and will require some custom technical implementation.
-JC
コメントを表示 · 投稿日時：2022年3月08日 · Jean-Charles Pascale
0
フォロワー
0
投票
0
コメント
Jean-Charles Pascaleさんがコメントを作成しました:
Hi Eune,
According to my tests, it seems like this is only available to Administrators and the agents themselves. However, the Team Lead was not able to see the tab.
-JC
コメントを表示 · 投稿日時：2022年3月07日 · Jean-Charles Pascale
0
フォロワー
0
投票
0
コメント
Jean-Charles Pascaleさんがコメントを作成しました:
Hi Eune,
The playlist will not have any limit based on time for the results it displays. However, since this is fetching the skips from our API, Archived tickets will not be included.
I hope this clarifies the behavior of the feature.
-JC
コメントを表示 · 投稿日時：2022年3月03日 · Jean-Charles Pascale
0
フォロワー
0
投票
0
コメント
Jean-Charles Pascaleさんがコメントを作成しました:
Hi William,
If I understand correctly, you have a field that is hidden for light agents, but that is also set as "mandatory" for your agents to fill in, therefore preventing your light agents from submitting any changes to the ticket if the field is empty?
Does this field need to be mandatory/hidden from the light agents?
The main workaround here that I could see would be to add a warning when a mandatory field is hidden, as we cannot override the field being set as "hidden".
-JC
コメントを表示 · 投稿日時：2022年2月28日 · Jean-Charles Pascale
0
フォロワー
0
投票
0
コメント
Jean-Charles Pascaleさんがコメントを作成しました:
Indeed, at the moment, to display an article to the end user using the Flow Builder, the article cannot be restricted to signed-in users.
As per a restriction on articles by still keeping them "Visible to Everyone", it should be possible via Custom code, but I do not have any template/example that I can provide for this.
I just know that they used the HelpCenter.user JavaScript object to detect if the user was logged in or not, like in this example to detect the organization of a user to hide some ticket fields in the form.
Hope this helps,
-JC
コメントを表示 · 投稿日時：2021年12月31日 · Jean-Charles Pascale
0
フォロワー
0
投票
0
コメント
Jean-Charles Pascaleさんがコメントを作成しました:
Hi Louis,
If you simply set a macro to set the title, then it should work immediately in the ticket indeed.
I attempted with a macro that sets the subject to {{ticket.title}} [{{ticket.organization.custom_fields.champ_org_dropdown}}] and it works as expected.
Could you confirm that the issue happens in any browser and in incognito mode?
Could you confirm that the issue also happens without the apps on your account? You can temporarily disable them for your session using ?noapps, as described in our documentation
-JC
コメントを表示 · 投稿日時：2021年11月10日 · Jean-Charles Pascale
0
フォロワー
0
投票
0
コメント
Jean-Charles Pascaleさんがコメントを作成しました:
When doing a similar test via APi, indeed, the placeholders are not replaced. Like I mentioned, even though in the API call you set the fields to a specific value, when the ticket creation in processed, those values do not exist yet in the ticket, and the placeholder therefore has no value.
However, when you submit the ticket again, the value is now there and the value is therefore replaced in the subject.
コメントを表示 · 投稿日時：2021年11月05日 · Jean-Charles Pascale
0
フォロワー
0
投票
0
コメント
Jean-Charles Pascaleさんがコメントを作成しました:
If I understand correctly, the correct data is populated on the second submission of the subject of the ticket.
If so, this is an expected behavior. Indeed, at ticket creation time, the organization of the ticket is not defined, and therefore the placeholder for ticket.organization.XXXXX has no real value. The placeholder is therefore not replaced.
When you update the ticket a second time, the ticket has a set organization, and therefore the placeholder has a set value and is replaced when the ticket is submitted again.
I hope this clarifies the behavior of the placeholders.
Kind Regards,
コメントを表示 · 投稿日時：2021年11月03日 · Jean-Charles Pascale
0
フォロワー
0
投票
0
コメント