- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2023 08:50 PM
Hi gurus,
I know you can link incidents to articles, but can you do the reverse with linking existing articles to existing incidents? We have a goal of having all our articles linked to incidents and was wondering on how to do this.
Solved! Go to Solution.
- Labels:
-
knowledge article

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-12-2023 12:37 AM
Hi,
You can add a related list "Attached to Task" to your knowledge base article view to achieve that. In that related list you will find the "Edit" button to related existing task. However technically you can add all task to a knowledge article so you may have to filter.
I hope that helps.
Kind regards Sebastian

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-12-2023 12:37 AM
Hi,
You can add a related list "Attached to Task" to your knowledge base article view to achieve that. In that related list you will find the "Edit" button to related existing task. However technically you can add all task to a knowledge article so you may have to filter.
I hope that helps.
Kind regards Sebastian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-12-2023 06:54 AM
We are achieving this using Service Operations Workspace and the Agent Assist pane. The pane surfaces KB articles that are likely relevant to the Incident (based on the Short Description). There is an Attach option in the article. By default, it places the Permalink URL in the Customer Visible notes and then immediately saves the Incident (which may lead to an email being sent to the Contacting Client). We modified the OOB action to put the URL in the Work Notes instead and the knowledge worker can decide if they want to send the URL to the customer or not.
The same workflow is available in Agent Workspace and the Agent Assist pane there.
In Classic UI, if the Related Search Results option is enabled, a search area is added to the Incident form, and KB articles are surfaced, and attaching is also possible.
I don't know what KM system you are following but I caution you on setting goals on attach rate. Knowledge workers will attach something just because they have to but it might not be relevant to the resolution of the INC. This then skews the data around which articles are being attached the most and the opportunity to use that data for process improvement.
We follow the KCS methodology which stresses setting goals on outcomes, not activities. If it's easy to manipulate, then don't measure it. We are looking more at the relevancy of what has been attached versus a 100% attachment rate.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2025 09:25 AM
Vickie, by default in my PDI, the Attach feature places a VERSION-SPECIFIC URL in, instead of a permalink. Do you know if you might have modified something to get that? It makes no sense to include a version URL instead of the permalink but I can't figure out how to change that. I made an onChange script to update the URL to use the portal URL so I can change the entire rest of the URL, but I still can't figure out how to get the KB Number in it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2025 10:24 AM
There are a lot of places where I agree with you about version-specific URLs (related knowledge articles come to mind) in the case of attaching to an incident, I agree with it being version-specific. It was that version of the article used. If the article is changed the day after the incident is resolved it would appear that the agent did not follow the changes - but they didn't exist the day before. Knowing which version of the article was used can be important for QA purposes.