Localization Framework for knowledge base and Service Operation Workspace

[Arnaldo]

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
Above solution are alternative to each other.
The enablement of LFS4KB is triggered by the 2 knowledge properties  that need to be set in this 
- glide.knowman.translation.enable_lf_article_translation = true
- glide.knowman.translation.enable_localization_framework = true  

With the enablement of above properties SN  recommends to disable   glide.knowman.translation.enable_translation_task = false

The effects of that property disablement is to remove 2 links  from UI Knowledge Form 

 Vs the enablement of the button for request translations in the knowledge article list 

@Alex Coope - SN 

We detected as well, that with enablement of LFS4KB,  in all workspaces is not possible anymore to request translations like it was possible before by Translation Management.

• Is there any specific reason for not enable to request translation from workspaces ? 
• If no, is there any plan for making request translations available from workspaces in the future releases ? 

Many thanks to anyone that would like to contribute to clarify 

Arnaldo 

[Alex Coope - SN]

@Arnaldo

The reason is "Translation Management" is a different product and feature which do quite different things (hence the different UI actions). And just so I fully understand, the ask here is around say an Agent in SOW to translate a workaround type of article?

Many thanks,
kind regards

[Arnaldo]

Many thanks for the fast feedback 

I understand that technically a framework is able to do more things but on the practical and operational side, the translation management subset of the framework (knowledge artifact) does the same thing as the previous translation management, i.e. it translates articles by generating tasks and generates draft articles from these tasks.
In addition, SN recommends the activation of LF4KB when translation of articles is needed.

For customers coming from previous versions where translation management was the only option, it is important to know whether removing certain features in new solutions is a strategy or a simple oversight.

Looking your answer, I understand that it is a strategy of ServiceNow to remove the ability to request to translate knowledge article  by means of Localization Framework from Service Operation Workspace or HR Agent workspace.

Thank you again for the clarification 

Arnaldo