Localization framework for knowledge article

Arnaldo
Tera Guru

In a multilanguage SN environment with Knowledge article versioning and dynamic translation enabled there 2 ways for translating article.
1 ) Translation management 
2 ) Localization Framework support for Knowledge Base
We are currently using the first solution and it is our intention to use the second.
From SN documentation
2 knowledge properties  need to be enabled 
- glide.knowman.translation.enable_lf_article_translation = true
- glide.knowman.translation.enable_localization_framework = true  

This SN property description recommends to disable   glide.knowman.translation.enable_translation_task = false
sys_attachment_java.jpg

 

 

The effects of that property disablement is to remove 2 links  from Knowledge Form 
2023-12-21_16-19-13.jpg 
The enablement of the 2 properties for Localization framework, allow to show 1 button in any Knowledge article list 
and the same button within the TAB Translated version of Knowledge Form 
From the Knowledge article list everything works fine, 
from TAB Translated versions of Knowledge Form we are getting  error "You must select one article at least

2023-12-21_16-28-08.jpg

 

Any suggestion comment on that ? 
@Alex Coope - SN 

3 REPLIES 3

Alex Coope - SN
ServiceNow Employee
ServiceNow Employee

@Arnaldo,

I think at specific UI action isn't intended to be used on a related list. When I last checked, it's intention was to be used on the base [kb_knowledge] table and you would have selected the English article to then be able to select what Language you would like to translate it to,

 

Also, the property mentioned is a side effect of the transition of the old "Translation Management" feature vs the migration to using the "Localization Framework" for KB article translations,

 

Many thanks,
kind regards 

--------------------------------------------------------------------
Director of Globalization Deployment, Internationalization

@Alex
Many thanks for the feedback .
The assumption to use "Request translation" from the related list looks like coherent with the disablement of the property that removes links Translate and Request translations from Related Link.
Those 2 links are visible just in the Original document but never in the translations.
Having possibility to request translation from  related list of an Original document is completely logic.  
BTW for your information  problem PRB1731056 is opened already for clarifying this aspect .   
Arnaldo 

Finally we get clarified from SN the usage of button Request Translations available in the Translated Versions TAB.
It is not possible to generate the first translation from the original article itself, it is always mandatory to start from the list of knowledge articles and select one or more original articles to be translated.

When there is an original article with its translations published, in the case of generating and publishing a new version of the original article, one may decide to generate a new version of the translation, always starting from the list of knowledge articles, as done the first time
or
from one of the available translations, go to the Translated Versions TAB and take the latest version of the original article to send the Translation Request and generate a new updated version of all translations.

Arnaldo_0-1706816426095.png