Forum Discussion

LynnStocks's avatar
LynnStocks
Community Member
3 days ago

Articulate Localization with Workday

Hi Everyone, 

I’m interested in learning more about how others are using the Localization (translation) feature in Articulate.
Are you currently using this feature in your projects?
If so, how has your experience been?
Has anyone successfully used it in conjunction with Workday?

For those using Workday specifically:
Does the integration provide visibility into which language a learner completed the course in?
Did this require any special configuration, or did it work out of the box?
I’d really appreciate any insights, best practices, lessons learned, glitches encountered and general feedback you’re willing to share.

Thank you in advance!

localization

1 Reply

  • AndrewBlemings-'s avatar
    AndrewBlemings-
    Community Member
    2 days ago

    My enterprise has been using Localization for a small while now and been a part of the Beta. We're using it to translate Storyline courses into multiple languages for diverse audiences.

    I'm unsure what you mean by "integration," since to me that suggests some sort of feature or third-party tool that creates extra functionality between Workday and Storyline 360, and I don't know of one.

    Everything I've seen so far suggests the 360 content runs in Workday just like any other SCORM output, regardless of the Localization. Launching a Localized course from Workday presents a small drop-down menu from which the learner selects an available language, and then when the learner does so, the course begins that version, but Workday has no hand in that and far as I know is entirely unaware of which language is chosen.

    Stakeholders of ours have expressed interest in learning which language a user selects, but I've seen nothing in the features of Storyline or Rise that suggests they send any additional information to Workday outside of standard SCORM content, and I'm curious how Workday would even know to handle it. Workday would need to store that information somewhere. 

    I've considered that the best workaround for the time being is to rig up a short answer question in the content, populate it with the language selected (which can be determined with a bit of JavaScript), and then sent back to Workday as a survey question where it'll be stored in Workday's interaction business object, but that interfacing isn't native to Storyline or Workday.