Storyline isn't currently designed to expose system variables for user interaction. As a result, JavaScript triggers that reference them could interfere with course playback.
I'd love to get more details on specific system variables you'd like to see and examples of how they could be used, and then I can share it with our team as a feature request.
I have a request, making templates for E-learnings, I created a menu page that allows to choose the scene you want to see. It should be very nice to be able to populate automatically the scene name in the menu to avoid a double entry of the name with all the possible mistakes link to that. It should be possible by giving access to the scene name using their IDs in the system variables.
I have the same request for the page name. it should be possible to access to any page name using its ID ( Scene number, Page Number)
Here is a partial list of some of the Storyline 3 system variables. I'm sure there are many more, but these are ones I was able to find from another project someone else had built.
Note that you cannot manually add these variables, because SL will not let you add the "dot" to a variable name...you have to begin with a project that already includes them in its variable list, so in addition to the Word doc, I'm adding a SL3 story file that uses all of them.
Copy and paste one of the slides into your project, and check your variables list...you should see all of these listed, in addition to any you've already added.
To use them, be sure to include the correct name. For example, to number pages in your project, use something like "%Scene.SlideNumber% of %Scene.TotalSlides%" or "%Menu.SlideNumber% of %Menu.TotalSlides%".
Note that there are four scenes in the project, but I've removed Scene 4 from the Menu and did not include any navigation method to go to the slides in Scene 4. Therefore, the Menu Total Slides and Menu Total Scenes values are different from those for the Project Total Scenes and Project Total Slides. While this may not have any practical use in a finished project, it is useful for development if you have project elements you want to store within the project for re-use on multiple slides. Therefore, when numbering pages with unviewable scenes or slides, you'll need to take that into account. One final note: be sure you've properly ordered the pages in the Menu, if you are using the Menu.xxx variables.
Also you'll see that in Scene 2, Slide 2, I've added a couple of layers. Note that none of the variables change, including page number, when viewing layers on a page. I'm sure there is a system variable for indicating which layer of a slide you're viewing, but since I don't know what that system variable is called nor could I add it manually, anyway, I've included it here for illustration only purposes. If someone has figured out what that variable name is and has included it in a project, I'm sure we'd all be grateful if you could include the .story file for us.
Hope this helps...I know for slide numbering, it did for me.
5 Replies
Hi Krzysztof,
Storyline isn't currently designed to expose system variables for user interaction. As a result, JavaScript triggers that reference them could interfere with course playback.
I'd love to get more details on specific system variables you'd like to see and examples of how they could be used, and then I can share it with our team as a feature request.
Hi,
I have a request, making templates for E-learnings, I created a menu page that allows to choose the scene you want to see.
It should be very nice to be able to populate automatically the scene name in the menu to avoid a double entry of the name with all the possible mistakes link to that. It should be possible by giving access to the scene name using their IDs in the system variables.
I have the same request for the page name. it should be possible to access to any page name using its ID ( Scene number, Page Number)
Thanks for those ideas, Eric! I've submitted them to my team.
Here is a partial list of some of the Storyline 3 system variables. I'm sure there are many more, but these are ones I was able to find from another project someone else had built.
Note that you cannot manually add these variables, because SL will not let you add the "dot" to a variable name...you have to begin with a project that already includes them in its variable list, so in addition to the Word doc, I'm adding a SL3 story file that uses all of them.
Copy and paste one of the slides into your project, and check your variables list...you should see all of these listed, in addition to any you've already added.
To use them, be sure to include the correct name. For example, to number pages in your project, use something like "%Scene.SlideNumber% of %Scene.TotalSlides%" or "%Menu.SlideNumber% of %Menu.TotalSlides%".
Note that there are four scenes in the project, but I've removed Scene 4 from the Menu and did not include any navigation method to go to the slides in Scene 4. Therefore, the Menu Total Slides and Menu Total Scenes values are different from those for the Project Total Scenes and Project Total Slides. While this may not have any practical use in a finished project, it is useful for development if you have project elements you want to store within the project for re-use on multiple slides. Therefore, when numbering pages with unviewable scenes or slides, you'll need to take that into account. One final note: be sure you've properly ordered the pages in the Menu, if you are using the Menu.xxx variables.
Also you'll see that in Scene 2, Slide 2, I've added a couple of layers. Note that none of the variables change, including page number, when viewing layers on a page. I'm sure there is a system variable for indicating which layer of a slide you're viewing, but since I don't know what that system variable is called nor could I add it manually, anyway, I've included it here for illustration only purposes. If someone has figured out what that variable name is and has included it in a project, I'm sure we'd all be grateful if you could include the .story file for us.
Hope this helps...I know for slide numbering, it did for me.
Kirk, you are a kind super wondeful man! ))