Getting job title from HR system to control learner experience (what content they see in course)

KatiePorter-68d​ this functionality is outside of the scope of Storyline. Storyline uses SCORM and xAPI and neither of these provide a means to get this kind of information on a user, unless using xAPI with an LRS and that information has been specifically included.

Whether this information is available through an API on Cornerstone will be up to Cornerstone and so it is best to check with them. If it is, then it will be relatively easy to integrate that API into Storyline and request that information from Cornerstone. It will require a JavaScript programmer to complete this for you.

Another method I've seen used is to allow users to select their role from a drop-down list of options. I know this system can be flawed as it may require updates and you have to consider user error, but if the roles are quite static, and you add confirmation dialogue boxes to any selection made, I think you'll be OK. I think this is the path of least resistance in terms of being able to achieve this without chasing up Cornerstone and a JavaScript developer to complete the integration.

In terms of showing different content within a Storyline course, that is straight forward enough as you would just control navigation using your defined "role" variable, e.g:

if role = "sales" go to this slide

if role = "support" go to this slide

The learner-specific data elements which SCORM 2004 provide are:

cmi.learner_id: Identifies the learner on behalf of whom the SCO was launched.
cmi.learner_name: Name provided for the learner by the LMS.

In SCORM 1.2, those elements are:

cmi.core.student_id: Identifies the student on behalf of whom the SCO was launched.
cmi.core.student_name: Name provided for the student by the LMS.

Both are accessed via JavaScript in Storyline using GetStudentID and GetStudentName.

There is no provision in the SCORM specification for Job Title, or for that matter, Email Address, as SCORM is a direct descendant of AICC, which also did not address those data elements. AICC did include additional student demographic data elements (address, title, familiar name, and so on) but they were not required and so most LMS' and development tools did not address them.

If the user's ID has that information embedded into it (e.g., the UserIDs of employees and our contractors use different letters to denote that what user-type they are, which I can then trap for in a course), you could control what the learner sees that way.

Hi KatiePorter-68d​!

Thanks for reaching out!

I noticed you've also connected with my colleague Lejan, through a support case. As he shared, Storyline doesn't support direct integration with APIs, so it's not possible to dynamically pull user data from an external source. However, we are tracking a feature request to implement this type of functionality. I've included your voice in the request!

In the meantime, I'll leave the floor open so community members can continue to share their workarounds and suggestions!