Configuration required for translation of knowledge articlesInstructionsCertain steps that need to be done depending on whether bulk translation is used or not. The starting point for knowledge translations should be from Knowledge management, rather than localization framework. Activating Knowledge Management Advanced (com.snc.knowledge_advanced) makes the entry in the "Localization Frameworks" ->Artifact Configurations for "Knowledge" with the Processor Script. In order to enable translation of Knowledge articles : - activate Knowledge Management Advanced (com.snc.knowledge_advanced) - activate I18N:Knowledge Management Internationalization Plugin v2 (com.glideapp.knowledge.i18n2) - Activate the languages that you want to do the translations for - Set the system property "glide.knowman.translation.enable_translation_task " to True ( add this property if it doesn't exist). This provides the option to request translations from the form view. - Set the system property "glide.knowman.translation.enable_lf_article_translation" to enable bulk translations. - Add entries to the translator mapping table so that the translation tasks are assigned to the appropriate individuals. When the system property "glide.knowman.translation.enable_lf_article_translation" is set to true, it allows for bulk requests ( i.e. request translation from list view) and uses the localization framework. In this case, the system property "glide.knowman.translation.enable_translation_task" can be set to false so that the option to request translation from the form view is disabled. The workflow preferences in localization framework are honored only if the translation is requested from the list view, not the form view. There are 2 UI actions of the same name - Request Translations. However, each of them serves a different purpose. (a) The one with sys_id=09e8613b73132300c1ad41244ef6a7ae is invoked from the form view ( ie. open a knowledge article and request translation). (b) The one with sys_id=fcaaa932c371011074658cab3c40dd8d is invoked from the list view - is intended for bulk translations where one or more articles can be selected for translation. The translation path here will follow the bulk route - ie, use the localization framework. These are not interchangeable - the UI script for the list view cannot be used for the form view. This is by design. The idea behind implementing the ability to request translation from list view is to allow for bulk translations and follow the workflow preferences, without losing the ability to translate articles one by one ( as from the form view). Note: (a) If the intent is to request translations only from the form view, then entries in Localization Framework -> Settings are not required. However, this means that translated articles will be automatically published. If the knowledgebase publish setting is set to "Knowledge -Approval Publish", then approvals will be required of that group. However, these individuals may not be the language experts. If the translation has to be approved by language experts, then the appropriate Localization Framework -> Settings have to be made and bulk translations should be used. (b) The workflow preferences you see in the Localization Framework ( Translate -> Publish, Translation → Translation Approval → Auto Publish and so on) are internal process flows / sequence of events - not actual workflows / flows ( i.e. the type one can see from workflow editor or flow designer). Ref doc link: https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/knowledge-management/task/activate-translation-mgt.html https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/knowledge-management/task/create-translation-assignments.html https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/knowledge-management/concept/conf-lf-settings-manual-translations.html