How overrides work
Eight permit field labels and the permit tile name can be overridden per installation in the system settings. The plant can therefore name a field the way its own procedure does, rather than the way the standard translation suggests.
The key rule: an override of a label takes priority over the translation in every language. If the administrator enters only a Polish name, a user of the English interface will see the Polish text in that place.
Practice 1: save the override in two languages
The override can be saved in two languages, Polish and English, and then the system chooses the version matching the user's language. This is the simplest way for contractors from abroad to see an understandable field name.
If the plant uses languages other than Polish and English, decide whether English is enough as the auxiliary language. The other languages supported by the system are German, Finnish, Russian and Swedish.
Fields with a Polish text on an English screen: example
Practice 2: start with diagnosis, not translation
When someone reports a Polish text on a foreign-language screen, first check the override settings. Only if the label is not overridden should you look for a missing translation in the language catalogue. The reverse order ends with adding translations that will be covered by the override anyway.
Final test on a live wizard
After a change, open the permit wizard in the target language and go through all eight fields. The settings do not show what the user will see; the screen does.
Practice 3: keep consistency with the printout
The printout layer has a separate translation key space from the interface. An override of a label on screen therefore does not have to change the wording of the document. After a change, generate a printout and compare it with the screen, so that the same field does not have two names.
Set an owner of the changes. At a group plant, field names are often approved by the head office or the legal department, so a name change made without consent may have to be reversed.
Common mistakes
The most frequent is a single-language override at a plant with a foreign workforce. The second is overriding one of the eight fields and leaving the rest with the old wording, which gives inconsistent vocabulary on one screen. The third is no test in the second language after a change.
Example from a plant with foreign contractors
At a plant where most permits are issued to contractors from abroad, field names should be unambiguous in both languages. Instead of internal abbreviations, enter the full term that someone outside the plant will understand.
A good practice is also a short walk-through with a contractor: ask one person from their workforce to read the screen in their language and point out the fields that raise doubts. It takes a dozen minutes and catches names the translation author does not see.
Record the result of such a review. When a new contractor from another country enters the plant, you will start from a ready list of remarks.
Checklist
Video
Frequently asked questions
Why do I see a Polish text on an English screen?
Usually because the label is overridden in the plant settings, and the override takes priority over the translation.
How many labels can be overridden?
Eight permit field labels and the permit tile name.
Does the override change the printout?
It does not have to, because printouts have separate translation keys from the screen. Check both after a change.
Check the labels in your instance
We will go through the eight permit fields with you and prepare the two-language override.
Let's talk