最近の検索
最近の検索はありません

Kay
参加日2021年4月15日
·
前回のアクティビティ2023年10月23日
フォロー中
0
フォロワー
0
合計アクティビティ
175
投票
19
受信登録
113
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Kay
Kayさんがコメントを作成しました:
For everyone looking at this topic, this feature can be utilised via an app in the Zendesk Marketplace: Macro Suite.
Agents can have the following prompts
- Single line
- Multi line
- Dropdown / Select
- Multiselect
- Datepicker
- Number
- Toggle
- Checklist
- One Time Secret
- Synced & Mirror
コメントを表示 · 投稿日時:2023年10月23日 · Kay
0
フォロワー
0
投票
0
コメント
Kayさんがコメントを作成しました:
For everyone following this topic.. There's an app known in the Marketplace: Macro Suite, which does just these things for Dynamic Content (and so much more)..
- Search for titles, descriptions and placeholders
- Create filters to manage locales on a regular basis
- Edit locales on a single page for each DC item
- Locale management in a single table
- Import/export (configurable) on Dynamic content
コメントを表示 · 編集日時:2023年10月23日 · Kay
0
フォロワー
0
投票
0
コメント
Kayさんがコメントを作成しました:
1) The feedback indeed goes to a special queue. In the community post you shared it links to a news requests page in the Help Center which creates a ticket where the feedback is stored.
2) Yes the code is indeed active for al pages that have an article. You could just create a new template for an article, where this code runs. Then when you're writing the article, select the newly created template, and only in that article this mechanism works. 💪
コメントを表示 · 投稿日時:2022年6月14日 · Kay
0
フォロワー
1
投票
0
コメント
Kayさんがコメントを作成しました:
At the moment it's not possible to do have a clean check if the user already has an open use case.
All though I do think this will be possible once Conversation Orchestration is more widely available.
Tip: Although there is something that comes close, it takes some effort to automatically close tickets when a user already has a ticket. This tip requires 1 custom User Field and 3 triggers.
1. Create a user field – Checkbox: User already has a ticket
This checkbox is located on the User Profile, and we need this to set and check against in the triggers.
2. Create a trigger – Auto solve user with a ticket
Conditions: [ Requester Field: User already has a ticket ] [ is ] [ checked ]
Action: [ Status ] [ Solved ]
3. Create trigger – Set the user field
Conditions: [ Ticket ] [ is ] [ created ]
Conditions: [ Requester Field: User already has a ticket ] [ is ] [ unchecked ]
Action: [ Requester Field: User already has a ticket ] [ checked ]
4. Create trigger – Uncheck the user field upon solve
Conditions: [ Ticket ] [ is ] [ updated ]
Conditions: [ Status ] [ is ] [ solved ]
Conditions: [ Requester Field: User already has a ticket ] [ is ] [ checked ]
Action: [ Requester Field: User already has a ticket ] [ unchecked ]
Of course, you can expand the triggers actions, and conditions to send messages to customers.
But it definitely helps manage the operational load for your team.
コメントを表示 · 投稿日時:2022年5月13日 · Kay
0
フォロワー
1
投票
0
コメント
Kayさんがコメントを作成しました:
Hi Damon,
The code I shared is working on multiple production Help Centers, the code from the article (whilst it also works) is heavily outdated and messy.
It also looks like something get's lost in translation. In your comment, you mention Groups instead of Organizations.
Both the code from Ruddy and myself are checking specifically against Organizations.
コメントを表示 · 編集日時:2022年5月13日 · Kay
0
フォロワー
0
投票
0
コメント
Kayさんがコメントを作成しました:
Dave Armlin – Checkout the latest comment here for a code sample.
コメントを表示 · 編集日時:2022年5月12日 · Kay
0
フォロワー
0
投票
0
コメント
Kayさんがコメントを作成しました:
Hi Damon,
May 12th, 2022 — For future people to read.
On this date dropdown values for the request pages are not stored in the DOM, because of that, it's only possible to delete the values when someone clicks the dropdown.
Solution
Here is the clean solution. Please remove all the code (you added) from your current sample.
It is Vanilla JS, jQuery free and not guestimating when elements are added to the DOM (no setIntervals).
I verified that this works and added comments in the code below, what each step does.
Don't forget to replace the form ID on this line.
// function that waits for the element to be added to the DOM.
function waitForElm(selector) {
return new Promise(resolve => {
if (document.querySelector(selector)) {
return resolve(document.querySelector(selector));
}
const observer = new MutationObserver(mutations => {
if (document.querySelector(selector)) {
resolve(document.querySelector(selector));
observer.disconnect();
}
});
observer.observe(document.body, {
childList: true,
subtree: true
});
});
}
// native JS way of waiting for the DOM to be ready
document.addEventListener('DOMContentLoaded', function() {
// Only run this code on the new requests pages
if (window.location.href.indexOf("/requests/new") > -1) {
// now let's actually wait for the element to be added to the DOM
waitForElm('.request_ticket_form_id .nesty-input').then((elm) => {
// the elements are now added so we can start binding the deletion whenever the click happens
document.querySelectorAll('.request_ticket_form_id .nesty-input').forEach((el) => {
// now we can bind whenever someone clicks on the form input, to delete one of the forms
// but only do this when the user is not part of organization
// in this example the next line checks for the organization with name: Managers
var isPartOfOrg = HelpCenter.user.organizations.find(o => o.name === 'Managers');
if (!isPartOfOrg) {
// replace the ID here with your Form ID
el.onclick = () => document.getElementById('6092785826321').remove();
}
})
});
}
}
コメントを表示 · 編集日時:2022年5月13日 · Kay
0
フォロワー
1
投票
0
コメント
Kayさんがコメントを作成しました:
Damon Maranya the code from the screenshot :)
コメントを表示 · 投稿日時:2022年5月11日 · Kay
0
フォロワー
0
投票
0
コメント
Kayさんがコメントを作成しました:
Please copy the code here. I will double-check it and convert it to working JS (there's absolutely no need for jQuery here).
Are you sure the user you test with is in the Organization with the name 'Managers'?
コメントを表示 · 投稿日時:2022年5月11日 · Kay
0
フォロワー
0
投票
0
コメント