- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2014 02:10 AM
Hello! I have been searching for solutions for a problem i have on knowledge Base.
In my company we want to add KB's , only FAQ's (topic) on our ESS portal. The issue is that we have users based in 4 regions (Norway, Sweden, Finland and other (english speaking)). This means that our articles are written in four languages. I solved that by adding some additional topics choices: FAQ_NO, FAQ_SE and FAQ_FI however, i would like to have one page in the ess portal that displays KB's based on the country/language the logged on user has: Norwegian = FAQ_NO, Swedish = FAQ_SE, Finish = FAQ_FI, English = FAQ
This is easy if i apply the KB International plugin (I18N: Knowledge Management Internationalization Plugin v2) . BUT then i run into another problem. Because, we have other KB's that are not country specific, and with this plugin, one have to specify language for each KB with the result that users are restricted to view KB's in their language.
I would like to have to options on the portal:
1) view country specific FAQ's
2) view global FAQ's + option to view other countries FAQ's.
So my thoughts are:
Option 1) add some kind of condition that checks the language for the logged on user and displays topics accordingly.
option 2)If i have the plugin activated, there must be some way to override the language on some topics...
Unfortunately coding (jelly, javascript) is not my strong side, so any ideas?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2014 03:19 AM
We have similar issues and use this
Our users are all AD integrated so we can use the DN as well

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2014 12:40 PM
Hi Ingrid,
I received your email related to this topic, as well, but I want to make sure any responses you receive are available to the rest of the Community.
Don't worry...coding isn't my strong suit, either. I have not implemented internationalization for the KB, but it sounds to me like what you're looking for are user-editable filters. This means you wouldn't prevent access to articles with roles or ACLs, but you would automatically show only the articles in the user's preferred language. Think of a getUser function, typically used for filters like My Open Changes, My Work, or My Problems. These automatically limit what the user sees when they click the application, but they can increase their view by changing the filter. I believe the same could be done with language because there must be a table, which contains the country/ language of all your users, even if it's just the sys_user table. It might take some dev time to make that option available in a kb_home or kb_find situation, but I think that might help you both separate the content and keep it together for those who want to see it all.
Another suggestion would be to add an auto-filter application for each language/ country. This would work the same as the function above, but wouldn't be user specific. Instead, the filters could just be set up to separate the content, and the user would pick which language they wanted to search. This would also provide the option of expanding the search to other countries, or you could create an All Countries/ Languages filter that had all published content.
Again, I'm not clear on internationalization, but these are some examples of how I would filter content if I wanted to tailor it to fit the individual while maintaining it in one repository.
I hope that helps!
Britt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2014 11:36 PM
Hello. sorry for late reply- have had vacation for a few weeks. i will have a look now. and get back to you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2014 03:19 AM
We have similar issues and use this
Our users are all AD integrated so we can use the DN as well