How do you modify the side-by-side translation form?

Forrest  Falk
Tera Guru

Hello,

I am trying to figure out where to modify the side-by-side translation view on a translation task. The view has some fields I would like to remove and reorder. I tried right-clicking the top banner, and nothing happened, so I cannot configure the layout. How can I change the view of this form?

 

You can get to it by going to a knowledge article and clicking the "translate" UI Action in the related links. The UI Action appears to redirect to the kb_create_translations table. I have also included the associated docs of how to open a translation in translation management below. 

 

Screenshot of knowledge article:

 

Knowledge Form to Translate.png

 

 

Screenshot of translation task side-by-side view:

Side by Side Translation.png

Link to Translate a Knowledge Article from a Translation Task:

https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/product/knowledge-management/task/...

 

Thank You!

1 ACCEPTED SOLUTION

@Forrest Falk,

Ok, so what's happening is that the artifact you are using is picking up all the "translated_fields" and "translated_text" fields (this is how artifacts work). The short answer is, you can't change this behaviour in the comparison UI and you wouldn't want to as it would break the core functionality of the Localization Framework.

 

It looks like your [kb_knowledge] table has had quite a few fields added to it. When it comes to translated articles they work in a "parent" > "child" relationship, where the translated articles are actually on the same table and linked via the "parent" table. Therefore, there may not necessarily be a need for those fields to be "translated_fields" / "translated_text" fields as that logic wouldn't show in the child article in the way it is now.

 

It may be better to leverage knowledge templates with structured sections to the article's body instead and leverage the artifact as per the ootb concept,

 

Many thanks,

Kind regards 

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

View solution in original post

4 REPLIES 4

Allen Andreas
Administrator
Administrator

Hello,

Are you saying you want to hide fields from being translated? So they'd remain in English on the article if that was the parent article version language. Just trying to understand the use case and what the end goal would be. In addition to removing/hiding them...you mentioned reorder. Same type of question here, the order, I believe, is driven from the article template/form layout order where you have the order set there.

Please mark reply as Helpful, if applicable. Thanks!


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

Hi,

I'm glad you have found a response that helped you with your issue. If my reply above helped at least prompt you to provide more, such as your reply below that ultimately gave us more context/information for someone else to help get you the rest of the way, feel free to mark that reply as Helpful.

Take care! 🙂


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

Forrest  Falk
Tera Guru

Hi Allen, 

Thank you for the quick response!

The primary use case is to provide translation users with an intuitive UI. Right now duplicate fields are showing on the form, such as short description, description, and workaround fields. If one of the duplicate fields is updated and the other is not, it will only take the value of the first field. This shows a problem since values are only filled in one of the fields from the translation module (see screenshot below). I am trying to update the layout so I can remove those fields. Do you know where I may be able to change the layout of this form?

Duplicate fields on translation side-by-side:

Example of duplicate fields.png

I tried right-clicking on the top banner, and it does not let me change the layout.

ForrestFalk_0-1676041836196.png

I also checked the Form table (sys_ui_form), and there are also no forms for the table:

No form records in kb_create_translations.png

Please let me know if you have any questions.

Thank you!

 

@Forrest Falk,

Ok, so what's happening is that the artifact you are using is picking up all the "translated_fields" and "translated_text" fields (this is how artifacts work). The short answer is, you can't change this behaviour in the comparison UI and you wouldn't want to as it would break the core functionality of the Localization Framework.

 

It looks like your [kb_knowledge] table has had quite a few fields added to it. When it comes to translated articles they work in a "parent" > "child" relationship, where the translated articles are actually on the same table and linked via the "parent" table. Therefore, there may not necessarily be a need for those fields to be "translated_fields" / "translated_text" fields as that logic wouldn't show in the child article in the way it is now.

 

It may be better to leverage knowledge templates with structured sections to the article's body instead and leverage the artifact as per the ootb concept,

 

Many thanks,

Kind regards 

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