Need to understand the configurations related to localization framework for Knowledge Articles

[Shalini]

In localization framework, after publishing the translation task related to Knowledge article, the Draft version of knowledge article is creating for translated version. Just need to understand from where the configuration is done for the knowledge article creation for translated version (child article).  Because we need to restrict some fields, so that it should not copy from Parent to translated version article (Eg: Tags).

@Alex Coope - SN

@Ankur Bawiskar 
@Harsh Vardhan 
@asifnoor 
@Jaspal Singh 
@Sandeep Dutta 
@Edward Rosario 
@Alisa Tipisova 

[kaushal_snow]

Hi @Shalini ,

In the ServiceNow Localization Framework, when translating a Knowledge Article, a draft version (child article) is created to maintain the relationship with the original article. By default, certain fields, such as tags, are inherited from the parent article to the translated version. To restrict this behavior and prevent specific fields from being copied, you can implement the following configurations:

1. Modify the Localization Framework Script Include

The KnowledgeTranslationUtils Script Include handles the creation of translated articles. You can extend or modify this Script Include to exclude certain fields, like tags, from being copied during the translation process....

var translatedArticle = new GlideRecord('kb_knowledge');
translatedArticle.initialize();
translatedArticle.parent = parentArticle.sys_id;
translatedArticle.language = language;

2. Implement a After Insert Business Rule to Clear Tags Post Creation

Table: kb_knowledge and Condition: current.language != 'en' (or your base language)

if (current.language != 'en') {
current.tags = '';

3. Configure Field Level Security

To prevent users from manually adding tags to translated articles, you can configure field level security....

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

[Alex Coope - SN]

Please do not modify the ootb script - this is an unnecessary customization that could break various functionalities.

@Shalini,
Your best bet might be to create a new Business Rule on the [kb_knowledge] table for articles that have a different language (e.g. condition of "language!=en") and remove the field values in question that way. That should be a pretty clean way of handling such a requirement, so if something in the future comes along you can just disable your new Business Rule,

Many thanks,
kind regards