I'm new to using Engage 360, excited at the opportunities with that tool. I was hoping I could publish my interaction (check list) to my Rise course like I can a storyline piece in Review 360, but it's not showing up in my Review 360 published courses once I publish it. It says it can only do Storyline courses, so I assume that's why.
Is it possible for me to add my Engage Interaction to a Rise Course, and if so, what's the best / easiest way to do that? Do I need to save it in Presenter as a slide?
I have also imported an Engage interaction into SL360, and followed all the steps as Tom has written. However, I get an ugly gray play button to "play" play the interaction, when launched in Chrome, but the play button doesn't appear in IE.
the play button is generated by the browser when there's media; you could create a first slide without media and a trigger to jump to the other slide when timeline starts
Thank you for your response. I did exactly that workaround then published to review 360 and inserted a SL block in rise. I still get the play button to launch the engage interaction. I also tried putting an image on the first slide and a hot spot to click and go to the engage interaction. It still get the play button.
Thank you again, Tom. I am grateful for your guidance and input.
In my research, I've found other posts that indicate Engage interactions are treated as Web Objects and place a play button. On one post here, Jen had a similar work around to me, which I did. And I got the play button. Now, I launched her workaround in Chrome and it launched without a play button; same in IE . I'm puzzled why mine isn't working when launched in Chrome. It does work fine in IE, but it's not our company default browser.
I've attached the engage file. I've set my SL360 web object to load automatically and I've set menus and controls to off.
I found if I start in Rise and then click into the lesson the play button won't show. When I start at the lesson with Engage, it does show.
I tried a couple of things with a started slide, which didn't work. And then moved the interaction to a layer, and started with no interactive elements. That didn't work either.
Essentially, the browser is stopping the media from auto starting until the user engages it. That's be design. Usually you can kind of workaround it with the previous tips, but it looks like the Engage interaction is handled differently (as you noted it's treated like a web object).
Version of Storyline isn't important at this stage, it's the browser that
generates the "wall" so to speak. It's to prevent media from just
autostarting and gives the device owner control over when to activate it.
I enlisted the assistance from Jen in the post here and I think there is a version issue; just not with Storyline. It's with Engage.
When I publish her SL360 with her engage interaction, it launches just seamlessly in Rise in Chrome; no ugly gray play button. When I add my engage interaction to her SL360, placed either before or after her engage interaction, I get the ugly play again. If I import her engage interaction into my SL360, it launches seamlessly. I think the issue is with my engage. I have version 4.23.18834.0. I'm not sure what hers engage version is, but I'm thinking it's more recent than mine. She has studio 5.25.21221.0.
If you are willing to test this, the files are in the original post, and you have me engage from yesterday. It's mind boggling.
I tested using Jen's example as you indicated and it's working as expected for me. I see where you reached out here as well and Crystal confirmed the latest update for you.
You can take a look at my sample using Jen's starter and your Engage interaction here. Let me know if that plays as expected for you.
If so, we certainly recommend downloading the latest update.
I appreciate your input Leslie. When I click on your example, I get the ugly play button. We have an Enterprise License and our upgrades are managed by IT and making sure they are stable in our LMS.
Good news! There are two workaround options to get your Engage interactions into Rise 360! Below is a quote from Tom who offered up these options previously in this conversation.
Tom Kuhlmann
You have two options:
Publish the Engage file and put on a web server and the use the Rise embed block and an iframe.
You can import the Engage interaction into a single Storyline slide. Turn off all the SL player features. Then insert as a Storyline block.
I hope this helps you out! Thanks for reaching out!!
Thank you for your response. That's not exactly the situation that I'm having (or in this thread). I am inserting an Engage interaction into a Rise course. I tried all of the methods in your video but still end up with the big gray play button in my Rise course.
I'll play around with some ideas and see what I can get. Which Engage interaction are you using?
Personally, I'd build that interaction in Storyline if possible, which eliminates inserting one's app output into another app's output into another app.
31 Replies
You have two options:
Thank you! The SL approach worked perfectly. =)
Hi Tamara,
I have also imported an Engage interaction into SL360, and followed all the steps as Tom has written. However, I get an ugly gray play button to "play" play the interaction, when launched in Chrome, but the play button doesn't appear in IE.
Any suggestions?
Thanks!
the play button is generated by the browser when there's media; you could create a first slide without media and a trigger to jump to the other slide when timeline starts
Hi Tom,
Thank you for your response. I did exactly that workaround then published to review 360 and inserted a SL block in rise. I still get the play button to launch the engage interaction. I also tried putting an image on the first slide and a hot spot to click and go to the engage interaction. It still get the play button.
Any other thoughts?
It's possible that the Engage interaction itself is seen as click-based media?? Can you share the file, I can look at it and perhaps offer some ideas.
Thank you again, Tom. I am grateful for your guidance and input.
In my research, I've found other posts that indicate Engage interactions are treated as Web Objects and place a play button. On one post here, Jen had a similar work around to me, which I did. And I got the play button. Now, I launched her workaround in Chrome and it launched without a play button; same in IE . I'm puzzled why mine isn't working when launched in Chrome. It does work fine in IE, but it's not our company default browser.
I've attached the engage file. I've set my SL360 web object to load automatically and I've set menus and controls to off.
Thanks for your thoughts.
How is this playing for you?
http://articulate-heroes-authoring.s3.amazonaws.com/Examples/Rise/Engage360/1Slide/index.html#/lessons/CfnjqwU1DUrPtixmv-lIABLg3ick4_R4
I tried in FF, Edge, and Chrome and it works for me.
Hmmm...I have a theory. What version of SL360 and/or Articulate 360 desktop are you using?
Using your link above, I get a play button.
I found if I start in Rise and then click into the lesson the play button won't show. When I start at the lesson with Engage, it does show.
I tried a couple of things with a started slide, which didn't work. And then moved the interaction to a layer, and started with no interactive elements. That didn't work either.
Essentially, the browser is stopping the media from auto starting until the user engages it. That's be design. Usually you can kind of workaround it with the previous tips, but it looks like the Engage interaction is handled differently (as you noted it's treated like a web object).
Here's what I see, if that is any help.
https://360.articulate.com/review/content/84a85dac-23b2-449c-93c7-33d0d51695a6/review
Hi Tom. I will experiment with the options. Would it have anything to do with the version of SL360?
Thank you again, I am very thankful for your insights.
Version of Storyline isn't important at this stage, it's the browser that
generates the "wall" so to speak. It's to prevent media from just
autostarting and gives the device owner control over when to activate it.
Hi Tom,
I enlisted the assistance from Jen in the post here and I think there is a version issue; just not with Storyline. It's with Engage.
When I publish her SL360 with her engage interaction, it launches just seamlessly in Rise in Chrome; no ugly gray play button. When I add my engage interaction to her SL360, placed either before or after her engage interaction, I get the ugly play again. If I import her engage interaction into my SL360, it launches seamlessly. I think the issue is with my engage. I have version 4.23.18834.0. I'm not sure what hers engage version is, but I'm thinking it's more recent than mine. She has studio 5.25.21221.0.
If you are willing to test this, the files are in the original post, and you have me engage from yesterday. It's mind boggling.
And, I'm grateful for your assistance.
Hi Lisa,
I tested using Jen's example as you indicated and it's working as expected for me. I see where you reached out here as well and Crystal confirmed the latest update for you.
You can take a look at my sample using Jen's starter and your Engage interaction here. Let me know if that plays as expected for you.
If so, we certainly recommend downloading the latest update.
I appreciate your input Leslie. When I click on your example, I get the ugly play button. We have an Enterprise License and our upgrades are managed by IT and making sure they are stable in our LMS.
Hello, I know this thread is almost 2 years old, but I'm experiencing this issue. Is there any resolution? I'm using Engage 360.
Hi, Alison!
Good news! There are two workaround options to get your Engage interactions into Rise 360! Below is a quote from Tom who offered up these options previously in this conversation.
I hope this helps you out! Thanks for reaching out!!
I should have been more specific. I am having the issue with the big gray play button.
Here's a video I did about the play button.
https://www.youtube.com/watch?v=Kn6bASbh8Hs&list=PLN1D8nyF9qR_DGA3zmyRs-42hfpEmnrWm&index=6&ab_channel=learningppt
Hi Tom,
Thank you for your response. That's not exactly the situation that I'm having (or in this thread). I am inserting an Engage interaction into a Rise course. I tried all of the methods in your video but still end up with the big gray play button in my Rise course.
I'll play around with some ideas and see what I can get. Which Engage interaction are you using?
Personally, I'd build that interaction in Storyline if possible, which eliminates inserting one's app output into another app's output into another app.