An application is calling a help file and I want to let the application call my storyline project as helpfile. The point is that I would like to have the help context sensitive so the Storyline project needs to start on different slides, depending on where in the application the user calls for help.
Is there some way that I can do this by adding a variable in the link that is calling my Storyline project? Can Storyline handle a variable this way? Maybe other solutions?
I have been searching in javascript threads in the community but these all have a different starting point. Also maybe I'm ending up with a monster-solution and perhaps there is a simple way that I don't know of.
Hello Klaas! You have an interesting idea; I haven't come across examples where Storyline has been used in this way. I'd be interested to see what you come up with! And gee, I hope it isn't a monster. ;)
Also, I'm not sure how large your Storyline file is, but if you expect that the different help "access" points are relatively segregated from each other, I guess you could publish each of those segments individually and use their respective links in your application. You'll jump to the right course, a.k.a. help file, and still maintain the interactivity that Storyline cultivates.
I am not sure yet how big the storyline project will be but if the project is relatively small than Chrystal's suggestion might be the most easy way. The problem that I see here when the project gets bigger is to keep the projects consistent and to share content between them.
I also am very interested though in Matthew's post as I was not aware Storyline can handle variables as parameters in a link. After digging further in the community forum I found the answer in this threat:
There's an example in this thread that uses a querystring fed value to jump to a slide. Would definitely recommend considering a simpler method first but this can work well and consistently. Depending on the number of "switch" conditions, not too difficult to implement.
6 Replies
Hello Klaas! You have an interesting idea; I haven't come across examples where Storyline has been used in this way. I'd be interested to see what you come up with! And gee, I hope it isn't a monster. ;)
Also, I'm not sure how large your Storyline file is, but if you expect that the different help "access" points are relatively segregated from each other, I guess you could publish each of those segments individually and use their respective links in your application. You'll jump to the right course, a.k.a. help file, and still maintain the interactivity that Storyline cultivates.
What Matthew said. The simplest ways are always the best.
Hi all,
Thank you for helping me on this issue.
I am not sure yet how big the storyline project will be but if the project is relatively small than Chrystal's suggestion might be the most easy way. The problem that I see here when the project gets bigger is to keep the projects consistent and to share content between them.
I also am very interested though in Matthew's post as I was not aware Storyline can handle variables as parameters in a link. After digging further in the community forum I found the answer in this threat:
https://community.articulate.com/discussions/articulate-storyline/passing-values-into-storyline
Thank you Matthew for convincing me that the URL solution should be there ;-)
There's an example in this thread that uses a querystring fed value to jump to a slide. Would definitely recommend considering a simpler method first but this can work well and consistently. Depending on the number of "switch" conditions, not too difficult to implement.
https://community.articulate.com/discussions/articulate-storyline/best-approach-for-internal-bookmarking#reply-65206
That's a great question. I think it is fine since the querystring doesn't shift. Would need to test that...
Well Steve, great addings to my case ;-). Thank you for these inspiring examples of how to use what is possible (with a bit more than storyline ;-).
I'll defenitly will have a good look at it later.
This discussion is closed. You can start a new discussion or contact Articulate Support.