Help with translation error

neil_jones
Giga Contributor

All of a sudden part of the "Comments (Customer Visible)" label on our incident form is displaying in French or German depending on the view.   Everything else on the form is displaying correctly in English.   If I change my system language to anything else other than English the form appears to display everything in the selected language as expected.

Default view:

find_real_file.png

Self Service view:

find_real_file.png

This is definitely a recent issue and I have tried to find out why this is happening but so far I can't even find where the different language options for the part of the label in parenthesis are configured, although I do have some experience translating other parts of the form.   If anyone can explain to me how I can configure the language localization for this field it would help a lot.

Thanks in advance

Neil

1 ACCEPTED SOLUTION

corina
ServiceNow Employee
ServiceNow Employee

Then, you can make the final test: when you see the issue happening make a cache.do


See if it gets solved.



I just came across a problem with exactly same description, should have been solved already, and if this is the problem, only the workaround can be provided.


Flush the instance cache when possible, alerting users that their temporary user session data will be wiped out.


View solution in original post

15 REPLIES 15

corina
ServiceNow Employee
ServiceNow Employee

Hello . yes you got it right.


Give it a try with the other one, something useful under the messages?


corina
ServiceNow Employee
ServiceNow Employee

What version are you on?


Helsinki


Thank you, I finally found the reference to "Customer Visible" and all the translations of it under "System Localization > Messages", however now that I've found it i'm still not sure why it is not displaying correctly because the en version looks normal to me, as do the others:


find_real_file.png


Regards,


Neil




corina
ServiceNow Employee
ServiceNow Employee

Then, you can make the final test: when you see the issue happening make a cache.do


See if it gets solved.



I just came across a problem with exactly same description, should have been solved already, and if this is the problem, only the workaround can be provided.


Flush the instance cache when possible, alerting users that their temporary user session data will be wiped out.