Forum Discussion

AndrewBlemings-'s avatar
AndrewBlemings-
Community Member
24 days ago
Solved

What does the Language condition of a trigger actually check?

Hello everyone,

I'm exploring the Localization features of a Storyline 360 Beta and came across the below in the KB article Create Multi-Language Storyline 360 Projects:

The idea of Articulate reading a user's language interests me, and creating contextual layers is pretty straightforward to me, but I'm curious if anyone knows what web property this Language condition is looking at?

For unrelated purposes, I was able to create a 360 file that called the lmsAPI functions, returning a GetLanguagePreference() of "en," so my org's Workday seems like it can communicate a condition, but is there any documentation that confirms whether this trigger

  1. discreetly runs the GetLanguagePreference() lmsAPI function,
  2. reads the system/OS language,  
  3. checks the Language chosen in Storyline's Player Text Labels dropdown of the Player Properties popup, or
  4. some other way?

In my org, the system language may not align with the user's preferred language so I need to know sooner rather than later if this trigger checks the system language so I can save myself from developing language layers with conditions that'll never fire.

Hope everyone's year is starting up,

AB

 

P.S. My personal Workday account shows a Default Display Language of English and a Preferred Display Language of "select one," so GetLanguagePreference() returning "en" suggests it chose the default language when the preferred was empty. Currently in my org, I can only choose English as a preferred language so I'm unable to test alternate languages on my own, hence the desire for documentation.

  • Received an internal response I understand as the trigger currently checking the user-selected language presented in multi-language content packages only.

    Word is that it's not currently accessible or changeable through JavaScript, but maybe the upcoming JavaScript API will change that.

  • Received an internal response I understand as the trigger currently checking the user-selected language presented in multi-language content packages only.

    Word is that it's not currently accessible or changeable through JavaScript, but maybe the upcoming JavaScript API will change that.