Configurable agent workspace translate errors in filtering. How to turn translations off?

[Miikka_M]

Hi, 

I'm implementing CSM configurable workspace for customer. When customer changes language to Finnish, other translations are kinda good by OOB, but in filters (for example if I filter cases in workspace) there's language mixed with english and finnish, as we can see from the picture below: 



Is it possible to change translations manually in these values somehow? Or is it possible to disable whole OOB translation in these filters since they are not working correctly? For example if client changes Workspace language to finnish, these filter values and whole filtering pop up would stay on english. It's better than this finnish-english "finglish" mix as it is as OOB. 

Best,
Miikka

[Robin John]

According to this KB Article, the translations should be in the Message table. Have you already tried creating the required translations?

[Alex Coope - SN]

@Miikka_M,

So there's a couple of things to unpack here,

What release are you working on (so that I can get our QA team to validate if it's an issue), also have you performed a cache.do since installing the Finnish language pack to ensure your browser has been told to download the strings?

I've just checked my Tokyo P2 instance with Finnish and it's showing the correct translation of "Aktiivinen" "On" "tosi" (might not be the exact same filter modal as the one in your screenshot, but the condition builder is the same):

As a side note, we also have a dedicated forum for these types of topics here (ideally that's where this post should be),

Many thanks,
kind regards 

[Miikka_M]

Hi, 

Thank you for your answer. Our client uses Rome version of ServiceNow. I did cache.do, logged out from instance, opened instance again and logged in with Finnish language - I still unfortunately get the same mix-language in filters. 

Best, 
Miikka

 

[Alex Coope - SN]

@Miikka_M,

Ok, I'll check with or QA team if it was a fixed in a post Rome upgrade (which is what I'm currently leaning to, because SanDiego included a lot of tweaks like this). To explain what I mean by that, is that the Language Packs are part of the family release, which means that we sometimes update translations between releases in various forms or another.

As Rome is now n-2 I'm sure the Customer is already planning on when they will upgrade either to SanDiego or Tokyo, so it would for sure be worth checking in an upgraded DEV environment that the translations are showing for them. My screenshot was from a Tokyo P2 instance, so I can confirm it is working as expected in Tokyo,

Many thanks,
Kind regards