It looks like the next and previous buttons actually run through the engagement.
Is there any way to prevent that? Specifically on the Circle Diagram or Accordion engagements?
It really negates the purpose of the engagement otherwise.
As a participant, why should I click the objects in the engagement when I have to use the next button to go through them anyway?
The likelihood is the reverse will happen. The participant will click the engagement, and then find out they have to run though it all again with the Next button in order to leave the slide.
This makes the engagement very problematic. Is there a way to prevent this issue?
Thank you for reaching out and sharing what you see with your Engage interaction within Storyline.
The next button displaying steps in the interaction vs. going to the next slide with no option to control the behavior is an issue that has been shared with our team.
For now, the workaround is to embed the interaction right into Storyline 360:
Unfortunately, I have been embedding the interaction in to Storyline. The Next button controls are greyed out (Please see attached), so I can't make any changes.
Your link refers to web objects, but I don't see how to turn the Engagement into a web object. I tried publishing the interaction to web, but the above linked instructions didn't work for the published files.
4 Replies
Hi Christopher,
Thank you for reaching out and sharing what you see with your Engage interaction within Storyline.
The next button displaying steps in the interaction vs. going to the next slide with no option to control the behavior is an issue that has been shared with our team.
For now, the workaround is to embed the interaction right into Storyline 360:
Adding Web Objects
Thanks for your help.
Unfortunately, I have been embedding the interaction in to Storyline. The Next button controls are greyed out (Please see attached), so I can't make any changes.
Your link refers to web objects, but I don't see how to turn the Engagement into a web object. I tried publishing the interaction to web, but the above linked instructions didn't work for the published files.
Thanks again for your help.
Hi Christopher!
I'm happy to clarify. You can upload the published Engage interaction to a web server and then grab the URL to enter as the link for a Web Object.
Please let us know if you have additional questions!
That did the trick! Thanks for your help.