See it in action FR
Menu

Episode 4 · 5:47

Learner memory across courses

A Storyline variable stays locked inside its course. Capture your learner’s first name and job title in a short Introduction, then let the “Customer apology” feedback use them in a second course.

YouTube loads only when you play the video. Watch on YouTube

Chapters

What you’ll learn

  • Keep what you know about a learner from one course to the next, using the Memory Hub
  • Personalize feedback with the learner’s data, even when some of it is missing

Before you start

  • The “Customer apology” Q&A slide from episode 2, imported into a Storyline course
  • Articulate Storyline 360, to create a short second project and publish both courses

Follow along

Step by step

Define the variables

  1. In the menu, under Memory, open Hub: the list of facts your slides can capture and reuse.
  2. Select New variable and type a Name you’ll recognize: “First name”. SlideMind fills in the Variable key, memory.first_name, and it no longer changes once the variable is added.
  3. Keep the global Scope: one value per learner, shared across all courses. Select Add variable.
  4. Repeat for “Job title”, which becomes memory.job_title.

The capture slide

  1. In your module, select New slide, keep Blank slide and choose the activity Memory capture: it saves values from Storyline without calling an AI. Name the slide “Learner profile” and select Create the slide.
  2. In Values to remember, select Add a variable, then click Memory key: the two variables from the Memory Hub are listed. Pick first_name, and its scope comes with it.
  3. In Authoring tool variable, type the Storyline variable that holds the value, exactly as it will appear in your project: Learner_FirstName. Do the same for job_title with Learner_JobTitle.
  4. Open Try it to simulate the capture: it shows what the learner’s memory would hold. Nothing is saved.
  5. There’s no ready-made Storyline slide for this activity: the Installation step gives you the code. Select Publish, then Copy the code.

Course 1: Introduction

  1. In Storyline, create a new, short project: the “Introduction” course, with one slide.
  2. Add two text variables with the same names as in SlideMind, Learner_FirstName and Learner_JobTitle, two text entries that store into them, and a Continue button.
  3. Select the button and add a trigger: action Execute JavaScript, when the user clicks the Continue button. In Script, paste the code SlideMind gives you.
  4. Add a second trigger on the same button that jumps to the next slide, below the first one: the code from SlideMind runs first, then the course moves on.

Course 2: reuse the values

  1. Back in SlideMind, open the “Customer apology” slide, the one with Maya, and add two lines to its Instructions.
  2. Type the start of the first line, then type @ and pick “First name”: it becomes a pill. Finish the line, then do the same for the second one with “Job title”.
  3. Click each pill and, in If empty, show, type “not known”, then select Apply. A learner who never took the Introduction still gets clear feedback, and the AI never has to guess.
  4. Try it has no real learner, so the fallback is used. Select Save slide: the Storyline slide picks up the new instructions on its own, with no re-import.

Test in SCORM preview

  1. In Storyline, publish the “Introduction” project with Publish › LMS, as SCORM 2004. When it’s done, choose ZIP: Storyline packs the whole course into a single zip file. Do the same for the course that holds “Customer apology”.
  2. No LMS at hand? In SlideMind, under Test & monitor, open SCORM preview, SlideMind’s own test player. Use Choose a .zip for each package: SCORM or xAPI, up to 50 MB. Each workspace keeps up to three packages, for 24 hours.
  3. Select Launch for the Introduction, type test-learner-1 as the Learner ID and select Start. SlideMind treats it like a real learner, with a memory of its own. Enter the first name and job title, then select Continue.
  4. Launch the second course with the same learner ID and answer Maya’s question: the feedback speaks to Sam, with advice for someone on the phone. That course never asked.
  5. Select Relaunch as another learner: SlideMind starts fresh, with no name, just the fallback. In a real LMS, memory follows the learner ID that the LMS provides.

Transcript

Show

Scenario 3: Remember learners from one course to the next

Hi, and welcome back! Today, we'll capture a learner's name and job title in one course, and use them in another. Why SlideMind for that? A Storyline variable stays locked inside its course: when the course ends, it's gone. Your LMS tells SlideMind who the learner is, and SlideMind keeps what you choose to carry over, for any later course.

Define the variables

In the menu, under "Memory", open the "Hub": the list of facts your slides can capture and reuse. Select "New variable" and give it a name you'll recognize: "First name". SlideMind creates the technical key, and it never changes afterwards. We keep the "Global" scope, so every course can read it. Then a second one: "Job title".

The capture slide

Now, a slide that saves these values. Select "New slide", start blank, and choose "Memory capture": it saves values from Storyline, without calling an AI. We'll call it "Learner profile". Select "Add a variable", then click "Memory key": the two variables we just created in the "Memory Hub" are listed. Pick "First name", and its scope comes with it. Beside it, write the Storyline variable that holds the value, exactly as it'll appear in your project. Same thing for "Job title". "Try it" simulates the capture and shows what the learner's memory would hold. Nothing is saved. There's no ready-made Storyline slide here: the "Installation" step gives us the code. Publish the slide, then copy it.

Course 1: Introduction

In Storyline, a new, short project: our "Introduction" course. One slide, two text variables with the same names, two text entries, and a "Continue" button. This button is where we'll paste the code from our slide. Select the button and add a trigger. For the action, choose "Execute JavaScript". In "Script", paste the code. "When": choose "User clicks". The object: it's our "Continue" button. Then we'll add a second trigger on the same button: jumps to the next slide. Its trigger runs the code from SlideMind first, then moves on.

Course 2: reuse the values

Now, the second course: the one with Maya. In the "Customer apology" instructions, we add two lines. First: "Learner's first name:" Type @ and pick "First name": it becomes a pill. Then: "Use it once in your reply if it is known." Same thing for the second line: "Learner's job title:" @, "Job title". Then: "If it is known, make your advice fit that job." Click a pill to set what the AI reads when it's empty: here, "not known". That way, a learner who never took the "Introduction" still gets clear feedback, and the AI never has to guess. In "Try it", there's no real learner, so the fallback is used. Let's save: the Storyline slide picks up the new instructions on its own. No re-import.

Test in SCORM preview

Let's test. In Storyline, we publish our "Introduction" project for an LMS, as "SCORM 2004". When it's done, choose "ZIP": Storyline packs the whole course into a single zip file. Same thing for our tutorial course. Two zips, ready to test. No LMS at hand? SlideMind has its own test player: "SCORM preview", under "Test and monitor". Drop the zips your authoring tool published, SCORM or xAPI, up to fifty megabytes. Each workspace keeps up to three packages, for twenty-four hours. Here: two packages, two courses. We launch the "Introduction" and choose a learner ID. SlideMind treats it like a real learner, with a memory of its own: "test-learner-1". "Start". "Sam"… "Phone support agent"… "Continue". Now, in the second course with the same learner ID… Let's answer to Maya's question… and, here we go, the feedback speaks to Sam, with advice for someone on the phone. This information comes from what SlideMind knows about this specific learner. And it doesn't stop at a name and a job: you could pass along a score, an answer from an earlier course, a summary of a past conversation… The ways to personalize are endless. Relaunch as another learner, and SlideMind starts fresh: no name, just the fallback. Let's recap what you learned today. You created variables in the "Memory Hub". You built a "Memory capture" slide that saves values from Storyline. You used those values in another slide's instructions, with a text for when they're empty. And you tested two courses with one learner ID, in "SCORM preview". In the next video, we'll explore other ways to present these interactions to your learners. See you there!

Keep the idea going.

Bring one Storyline activity.

Start with a question worth answering. Build the feedback around your learning objective, then test it in your own course.