App translation

Support, Troubleshooting, & Help
, ,
1

Hello everyone,
I am looking to have some sort of trigger at the beginning of my app to enable the operator to select his language. I saw that there was some conversations about an AI translator trigger but I could not find it in the drop-down list under ‘Then’ in the Trigger section. Is anyone can help me ?

2

Hi @LucasLemaire,

Welcome to Tulip Community! :tulip: :tada:

I think the easiest way to accomplish this is to have the operator select their language in the Player menu

image
image2920×1040 179 KB

You can also select a default language per user in the User Profile to streamline this as well.

image
image1588×1196 61 KB

This article has more details on this: Multilingual Feature in Tulip

To answer your question around where to find AI translations in the trigger editor, the action can be found under “Frontline Copilot.”

image
image2190×1450 230 KB

I can see this article Translate could use some updates, so I apologize for any confusion there and we will update that shortly!

Let me know if this helps or if you have further questions :slight_smile:

3

So when I do that, it pops up with this error and won’t let me begin an app, the app works in english just fine until I go to change to Spanish? How do I fix that?

image
image705×711 10.4 KB

4

Hi Tyler,

That message usually appears when the Player is trying to update the app after a language change but can’t complete the update.

Please try:

  1. Publish the latest app version and assign that published version to the station (avoid using the Development version).

  2. Verify Spanish translations are enabled and complete in the app’s Languages settings.

  3. Restart or log out/in of the Player to refresh the app.

If it still happens, let us know which app version is assigned to the station and whether you’re using the desktop or browser Player.

5

It works but only as long as you are in the “most recently published version”. It will not work in the development version.

6

Hi Tyler,

Thanks for confirming. That behavior is expected. Language switching is supported when apps are run in the Player, while Developer Mode is a testing environment with known limitations and may not behave the same as production. Because of that, runtime language changes can fail in Development but work correctly in the most recently published version.

Best practice is to build in Development and validate multilingual behavior using a published app version assigned to a station.

Let us know if you need help with anything else.