- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2016 12:02 AM
Hi all,
This is also a known issue at servicenow but has anyone found already a workaround on how to make attachement visible on kb articles via the Self Service portal?
Regs,
Lô Mouhamadou
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2016 09:55 PM
Quite a few users have had this issue as well. Please view my response on a previous thread - Attachments don't get displayed in the new portal (Helsinki)
You can also download the widget I created on share - ServiceNow Share
The widget will display the attachments as downloadable links if "display attachments" checkbox is checked on the article and the widget is placed on the KB_article page.
Please let me know if you have any other questions!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2016 03:50 AM
Fix is available in helsinki patch 5 and Istambul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2017 11:48 AM
What do you mean that a fix is available in Helsinki Patch 5?
Are you saying that the workaround that was provided earlier in this thread works with Helsinki Patch 5 and above? Or are you saying that attachments for Knowledge articles in the Service Portal should be fixed as of Helsinki Patch 5 (or Istanbul)?
If you're saying the latter, I would have to disagree. I have a Helsinki Patch 7 instance and an Istanbul instance and neither one has the attachments functionality working for Knowledge articles viewed via the new Service Portal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2017 03:45 AM
Hi, the work arround is working from Helsinki version.
In the helsinki release patch 5 servicenow mentionned that the issue will be fixed.
So, no need to disagree with me because I just shared servicenow post.
If in your case it is not working, you can use the workarround