user
@benjaminjones
Trying to get the widget into Storyline?
I have filled out the sections of the Dialog builder and completed this, however I am confused on how to actually get this into Storyline.

As per the instructions, it states you need to add a trigger containing the JS presented. If I use a trigger in SL to execute the JS upon timeline starting, nothing happens, I've even added the other JS in the same way to no success.

Feel like I am missing a step, can you please confirm and outline the correct process please?
reply
Reply
user
@support
Hi Benjamin. Please upload your .story file, we'll check what's wrong. Note that we only need the one or two slides with your triggers, not the entire course.
reply
Reply
user
@benjaminjones
Hi Support,

I am unsure on how to share a file via this discussion thread. Please can you provide me an email or method of sharing this with you?
reply
Reply
user
@support
https://wetransfer.com/
https://google.com/drive
https://dropbox.com/
https://box.com/
reply
Reply
user
@benjaminjones
Hi there,

I have managed to upload this via Dropbox and here is the link to the file: https://www.dropbox.com/s/idd3dwzfbi6xt5p/Dialogue%20Function.story?dl=0
reply
Reply
user
@support
1. In your dialog setup, the third response option in step 3, you just pasted a URL (https://www.typeform.com/) in the "Execute JavaScript" box. This is not a valid code, so when the browser tries to interpret it, it breaks. This is the reason why nothing loads - the code breaks before it even executes.

2. The second trigger in Storyline (DialogShow();) seems redundant because when the first trigger completes, the dialog will load by itself. Additionally, as it's written now, it executes before the code finishes loading, which also has a potential to break the browser. Though I don't see it happening, but just a warning that it's better to remove it.

3. The third trigger (DialogOpen();) also the way it's written executes before the first code loads. So since there's nothing to open at that point, it might be an issue with some browsers. Same as #2, I don't see it happening, but just a warning that it's better to remove it.

So, to summarize, #1 is the reason why it doesn't work - this needs to be addressed. #2 and #3 don't do anything, only provide more opportunities to break, so it's good to address them, but not necessary.
reply
Reply