Forum Discussion
Has anyone built scalable adaptive logic in Storyline?
Hi everyone,
I know Storyline can handle branching, variables, triggers, and custom logic, and I know AI Assistant can help with content creation. But I’d like to hear from people who have actually gone beyond basic branching.
Has anyone built and maintained, entirely inside Storyline, a truly solid adaptive experience with meaningful learner paths, multiple variables, and instructional logic that stayed manageable over time?
I’m especially curious about three things:
• How far you were able to push it inside Storyline
• Whether AI Assistant helped with anything beyond assets or text
• When the project became too complex or fragile to maintain
I’d really appreciate real examples or honest limits.
Thank you in advance. I look forward to your comments.
Slim
2 Replies
The AI Assistant is very new, especially relative to how long Storyline 360 has been on the market without any sort of AI embedded, so that probably won't feature in as many success stories as you might hope.
I was fortunate to be part of a team many years ago that developed a customer call simulator, reproducing the company's proprietary CRM in a simpler format replete with variables. A JavaScript file was then coded to contain and manage many different customer scenarios, essentially acting as a database of names, dates of birth, questions callers would ask, and more.
Two new hires, one role-playing a customer and one role-playing a customer service rep, would open the eLearning on their respective computers, the "customer" would select a scenario from a list on the customer screen, and then relay it to the "rep" would enter that number into a make-shift CRM interface on the rep screen. One eLearning that had two faces, a bit like two people playing the game Battleship with one game box. Each saw different interfaces that enabled them to see the same scenario pulled from the same JS "database" but contextualized on their respective screens.
I don't remember how many variables the project required but it was might've been over 80. A formal schema for naming the variables helped a ton, especially since I leveraged more than a few predicate functions. They made it very easy for the eLearning to trigger some of my JavaScript, the code to figure out whether or not a condition changed, and then return the result back to the eLearning's associated predicate variable. For instance the eLearning might have a boolean variable called isCallerValidated that would house the value of the isCallerValidated JavaScript function. Not that length is a particularly meaningful metric, but I recall the final .js file having over 1000 lines.
The CRM interface did have a few different gates for learners to work through before being allowed into the next section, for instance learners were required to demonstrate they'd understood the caller's problem and resolved the call by correctly documenting in the CRM. Only after that would a button appear allowing them to navigate to a debrief screen they'd discuss with their "caller" partner.
You will find a lot of people have done this, I built mine project that became a mini LMS where the user completed an assessment and this informed the rest of the course, it assigned modules (6/53) and then tracked completion, almost like a mini LMS.
Everything is possible, I leaned on a lot of javascript to do it.
