In this video, learn how to create a different type of variable that allows you to not only track module completion, but page-level completion within the module. This is a more detailed way of tracking learner progress at the slide level.
- [Instructor] Okay, so a common question that invariably comes up is, can I add more detailed feedback? This is great that we're tracking at the scene level, but what if I want to track that module one, slide one, has been started or viewed, and so on? And the answer is, of course, yes, you can, but there's something we should consider. Right now, we're using true false variables to track really kind of big-picture-wise, the completion of each scene. If I want to use a true false to track each of the slides or more than one slide, I'm going to need a specific true false variable for each of the slides, so module one, slide one, true false variable, module one, slide two, and so on. That's a lot of variables, and we don't really need to go that route. Instead, if this is what we want to do, a single text variable would work a lot better because we can change the value of that text variable at the slide level. Remember, variables only hold one piece of data, so let's rework just the first button here. We don't need to do all of these, but let's just rework this one to show what a text variable would look like so we could provide more detailed feedback. First thing I want to do is add that detailed feedback to our visual icon. Come down here to the states panel and you see that we already have the normal and the completed. I need to add a new one for in progress type state, so edit state, new state, and let's call this started, meaning that the module has been started. We'll just do one, and let's make that orange, right? So it's in progress, which is more than not even started and less than completed. Click done editing. Now I need to add a new variable, so I'm going to come over here and click the project variables button. I'm going to add a new variable, and that's a little different naming convention here just to make this really contrast with what we already have in there. Text variable, default value is blank, right? Go ahead and click okay, click okay, and I'm going to update this one to show that new variable. Now if I type it incorrectly, percent sign, mod one, underscore, text, variable, and you can type these in, of course. I just have to make sure that I spell it correctly. Let me double check real quick just to make sure. Mod, text variable, cool, that's good. Oh, I didn't type it in mods. Let's do this, mod one. There we go, now I have the other names. So that's just the downside. You have to make sure that if you're going to type it in, you type it in correctly, that's cool. So let's go into the slide view and add the triggers to adjust the variables. So we want to add an in progress for module one, double click the slide to come inside of it, and come over here to the triggers panel and we want to adjust that text variable we just created to show that this is now started. So what is it we want to do? We want to adjust our variable, and the variable this time is the text variable we just created. We want to set a value of, let's just call it started. It started when the timeline starts on this slide, great. I'm going to copy this trigger because I'm going to reuse it on slide three. Now slide three already has that true false variable, but we don't want to use that here. So I'm going to delete it, so goodbye, delete, but I am going to paste the one I just created. But I don't want it to say started here, right? I want it to say completed. Isn't this brilliant? This is why using the text variables make so much sense here because we can keep overwriting or changing or adjusting the single piece of data that it holds. So when it gets to slide three, this variable changes and it's now completed, but on slide one, it's set to started, cool. Jump back to the main menu and we just need to update the triggers to change this icon based on the value of that variable. So I have the original trigger that we set, so I can work from this, so double click it, and the first part of this trigger is correct. We're changing the state of module one to completed when the timeline starts. This is all perfect. However, I just need to change the condition. The condition here is that our text variable is equal to and in case I don't follow a good naming convention, equal to ignore case, a value of started, right? 'Cause I might type in started, something like that. So if I ignore the case, all lowercase for sentence case, title case, all that's going to be fine, started. Click okay. Actually, no, going to double click that. That's going to be completed. We need this to be completed if it's going to change the icon to completed, right? Click okay, I can copy this real quick and paste it and then let's just move it up so that it's grouped with the first trigger. And this time, we can change it to started. The custom state started if the value here is started. Brilliant, go ahead and preview your project. And the value is blank here for text variables. Since it doesn't have a value, it just doesn't show anything. Click it once to enter slide one. Let's jump back home and we should see that the variable says started and the icon is orange. Perfect, let's jump in here and now we're going to go to the very last slide and jump home, and now it's showing completed. So this is a great example of how you can provide more detailed visual feedback based on the completion of slides within the scene.
- Using variables for learning personalization
- Capturing and displaying the learner’s name
- Creating text-entry fields
- Validating input with conditions
- Creating branching quizzes
- Calculating quiz scores
- Adding conditional branching based on quiz score
- Creating custom characters
- Adding custom navigation with bookmarking
- Adding conditional triggers to record learner progress
- Showing additional feedback at the slide level
- Creating learning journals
- Randomizing scenarios with variables