Multilingual helplinks — contextual help in the user’s language

Helplinks (contextual help tooltips for form fields) can automatically display content in the user’s interface language. This means that when a user switches to, for example, English, they will see English descriptions of the fields — without any additional configuration on the frontend side.

How it works

1. The widget reads the interface language — the helplinks component automatically detects the current user language and passes it in the API request.
2. The system searches for helplinks in the related knowledge base — if the knowledge base has a multilingual code set and there is a related base in the user’s language, the system returns helplinks from that base.
3. No translation? No problem — if the target base lacks a helplink for a given key, the system will automatically display the version from the main base (usually Polish).

Step-by-step configuration

1. Link the knowledge bases — make sure that the PL and EN bases have the same multilingual code (see: related entry on multilingualism).
2. Create helplinks in the EN base — in the English knowledge base, create helplinks with the same keys as in the Polish one (e.g., crm_client_name). The key must match exactly.
3. Fill in the content in English — each helplink in the EN base should have English content.
4. Optional: link entries — if the helplink leads to a KB entry (through the “Entry” field), link the PL and EN entries with the same multilingual code so that the language switch works correctly.

What if a translation is missing?

The system is designed to never show an empty tooltip — some content will always be displayed:

• If a helplink with a given key exists in the EN base → the EN content is displayed.
• If the helplink does not exist in the EN base, but exists in the PL → the PL content is displayed (as a fallback).
• If the helplink does not exist anywhere → it is automatically created as inactive in the main base (for later completion by the administrator).