Producing 4 modules with custom pathways from 1 .story file?

Hi Michelle,

Actually, yes you can do what you are suggesting, and I've had to do this very thing.

What you need to make this work is variables. Create a variable called Department. Then you can decide which slide to show based on the Department variable. Or, you could show different versions of a slide, using the Department variable to show the correct layer. 

Set the variable default value for the department you want to publish, and publish out a module for the selected department. Change the variable default value, and publish out a module for the next department. 

Dave

Hi, Michelle,

Interesting problem. Here's how I'd do this:

• Create a number variable. For example, call it Path. Assume that the values will be 1, 2, 3, or 4, based on the department. (Or you could make this a text variable, and use dept names as the values.) 
• Use triggers with conditions to control the Next button where applicable. For example, as per your JPG, slide A would have these 2 triggers:
  • Jump to slide B with the condition that the value of Path is 1 or 2. 
  • Jump to slide E with the condition that the value of Path is 4.
• Before you publish each SCORM package, adjust the initial value of the Path variable to match the department. 

If you aren't familiar with variables and conditions, I suggest you check out the Tutorials and User Guides (https://community.articulate.com/articles/tutorials-and-documentation). They provide the real power in Storyline.

Here is a sample of a project with various paths through it. The problem is that it depends on the learner choosing the correct department.

Phil Mayer suggests a way to set the department variable (as suggested by Dave and Judy) that won't require you to publish 4 different versions, in this post: https://community.articulate.com/discussions/articulate-storyline/setting-a-variable-in-the-story-html-file

Thank guys, using variables is a GREAT idea! And Walt, thank you for that link, I'm very intrigued by the idea of just altering the variable in a .js file after publication.

I've finished my intro and am working on my technology modules now, so I will build in my custom path behavior as I go through. I'll be sure to report back and let the community know how this worked out for me.

Thanks as always articulate community!

Actually, read farther down. Phil has an idea that doesn't require you to go in and change the .js, which would require either 4 separate modules, or changing it for every user. Phil's most useful suggestion is to pass the variable in the URL, which would be done by each individual user as they access the module, not by you.

I'm going to 100% candid here....I don't entirely understand Phil's response...

As it is, in this case , I cannot leave the choice in the users hands - as this is compliance training I must ensure each group of people sees the correct content. 

I was just reading this to see if I could help and it was great to see Walt recommending my solution, the great thing using this is the user doesn't realise they are selecting the variable as they are following the url.  Thanks Walt!

Phil's option only works if you have the module on the internet, and send a link to users. Using his js, you would send each different group a link, changing the part after the ? to match the appropriate group. Then when they go to that link, the js uses the part after the ? to change the variable.

Reading your request again, I don't think it would work for you if you are delivering it as a SCORM package,which means you are using some sort of LMS.

So I think you are on the right track; create one .story file, publish it, make three copies of the published folders, go into the .js file on each one, and change the variable. Then upload all four to the LMS. For what you describe, you have to have four finished files, but can still make changes to only one .story file.

That is exactly correct Walt - I ultimately need 4 finished files that I can upload to a LMS, but I would like to have just 1 .story file.

I've been flat out developing content so far but hoping to do some publishing this week and test this suggestion out. I'll let the community know how it goes.

Thanks again for everyone's assistance here.

I ended up going with Dave Cox's suggestion - that is, have all my triggers dictating what slides to go to, what department name to show etc dependent on a variable, DEPARTMENT, and adjusting the value of this variable prior to publication. So I have 1 story file which I publish 4 times. This has worked very nicely.

In this instances I went with this solution rather than the javascript editing route as this is the method which my colleagues would understand easier, if they had to take over management of this project in future. 

I haven't tested the 1 publication, javascript editing solution proposed by Walt and Phil but I'm very intrigued by it, hopefully I'll have time to try this option soon.

Thanks to everyone!