The trial version of any Articulate software is a full version so it should work as expected. When you're testing the attached, are you testing within the intended publish environment or are you testing locally? Testing it locally could cause you to encounter security restrictions within the browser. Also, you mentioned working within a VM, and you'll want to ocnfirm that the documents folder is a local install on the VM. There are some documented best practices for working in a VM here (presuming you're in a VM on a Mac as well).
If you're testing within the publish environment and you're still not seeing it, could you also share a copy of the .story file?
Thanks Fabio for sharing that here - and I see that David recommends not including the HTML5 output for the Engage element, but he doesn't say anything about not including it for the Storyline final publish - so using the story.html or story_html5.html should work either way.
Is there any news on allowing Engage 13 interactions to be brought into Storyline 1? I on;y bought Engage 13 as I wanted to use it with my existing Storyline installation and I won't be upgrading to Storyline 2.
You won't be able to use the Import Engage functionality to bring it into Storyline 1, but you can use the method here - and it will operate in a similar way as the import does, placing the Engage elements in as a web object.
Are you using Storyline 1 or Storyline 2? Storyline 1 still does not have support for importing Studio 13 content, so you may want to investigate a method such as the one here.
If you're using Storyline 2, can you tell us more about the error message you're receiving or what's happening when you try to import the interaction? Please make sure you're following the directions here on how to import Engage into Storyline 2.
I have SL2 but wonder if engage importation work ok in it?
I am importing my engages 13 to presenter 13 and from there i am importing the PowerPoint into storyline 2
I want the engages to play in my SL2 course so user can not pass to next slide until the have seem all steps in presentations, Anyone knows how to do that. My engage es setup is Interactive "Show PREV-NEXT Butoons" but it doesn´t work.
As work around i imported the engages to Power(setup the engages in presenter to "Single Item" and "After viewing all steps") and then imported that PowerP into ST2, but l can still click next before the seeing all step in the engage.
You should be able to import your Engage interactions into Storyline, and you could also look at following the steps here to import them directly. That article will walk you through the choices in terms of how the next button should function including the specific "next" functionality within Engage. If you've imported them into Presenter first, you'll want to change the next/prev behavior as detailed here.
I have a project originally created in Storyline 1 with Engage '09 interactions from a previous Project. I was disappointed when we upgraded to Studio '13 that the interactions were not compatible. So much so, that we had a computer with Storyline 1 and Studio'09 to edit them easily.
We were told when our group attended the DevLearn convention in November that this issue had been resolved with Storyline 2 and Studio '13. Now I am in the middle of edits and cannot get the "Next Storyline Slide" button to to appear after the completing the Engage interaction.
I have custom buttons throughout the course and do not want to use the player buttons-they are not easy to control, waste too much space, and look odd on screens when they are not being used.
In the image it looks like it's greyed out and you're unable to select from those options? Is that the behavior you're experiencing? Are you able to share a sample .story file with us that has the Engage interaction embedded? Are you adding the Engage interaction as described here or pulling it in from a Presenter file?
When you reply via email your attachments or embedded images are not included in the forum post. Also the email signature is included, so you'll need to revisit this post if you want to edit it and remove your signature and attach the documents for us to look at.
That’s correct. The options have been greyed out from the beginning. I used the same steps to insert the file as in your link.
The files were original to a presenter file, then imported to Storyline 1. I have since imported the engage files directly into Storyline 2, but the results are the same.
When I am on the inserted Engage slide, I click on the slide and this “Engage Tools” menu comes up. The button I need to control “Next Slide” is greyed out.
Also in the link you sent it talks about editing options, and the controls look grey there too.
Thanks for sharing your files here and letting us take a look. I was seeing the same behavior myself, so I checked in with some other members of our team and it seems that the show "next slide" button is a legacy feature for Engage '09. Our team has updated the tutorial to reflect that here:
Show 'Next Slide' Button: Use this drop-down to control when the Next Slide button appears in the published interaction: Never, Always, or When complete. (This option is only available if you have Engage '09 installed.)
You'll need to utilize the player buttons to allow the user to continue on to the next slide.
That's unfortunate, especially since we were informed differently at the conference. I have no options since I already converted the course to Storyline 2 and now don't have time to redo edits for the interactions in '09.
I don't understand why your products are not compatible with each other. There are numerous posts from unhappy users that experienced the issue initally with the upgrade to Studio '13.
If Storyline 2 has been designed to accept Engage '09 interactions, then why not '13?
At least let me run Studio '09 and '13 on the same machine then. It's a big hassel having to use a separate machine to edit the interactions. :(
My apologies if I was unclear, but Storyline 2 does support Engage '13, but the default behavior is to utilize the same player across both the Engage interaction and the Storyline 2 interface. This was based on feedback that we heard from users, and therefore the option mentioned is greyed out when it's not an Engage 09 interaction. The "next slide" button is still a feature of Engage '09 so the option is left in there if you're also importing an Engage 09 interaction.
It is frustrating and perplexing that Articulate would make their newest product, Storyline 2 compatible with an old version of Studio ('09) and not compatible with the most recent version of Studio ('13). Experienced developers want to maximize the space on the screen and have advanced control over the navigation buttons. The prebuilt navigation buttons waste valuable space on every screen whether being used or not.
Being able to use Engage interactions in a Storyline course allows flexibility in development and the time it takes to develop. I have been able to freshen a Studio '09 course by upgrading it to Storyline and maintaining the Engage interactions originally created. Now I just have 2 sets of buttons. :(
I'm glad you were able to implement a method that would work for you, and Storyline 2 is compatible with both Engage '09 and Engage '13, but since they had different features they'll have slightly different behaviors within the course itself. You're welcome to share your thoughts on this here in the forums or if you would like it to go directly to our product development team you can share your thoughts here.
Let me elaborate a bit on the Engage that I mentioned above. I'm not sure if you are saying that you have both '09 and '13 files still, but Engage has to be installed and activated to import. Both versions of Engage are probably not installed, so not sure if you need upgrade those files first to the latest version that you are probably utilizing :)
81 Replies
Hi Fabio,
The trial version of any Articulate software is a full version so it should work as expected. When you're testing the attached, are you testing within the intended publish environment or are you testing locally? Testing it locally could cause you to encounter security restrictions within the browser. Also, you mentioned working within a VM, and you'll want to ocnfirm that the documents folder is a local install on the VM. There are some documented best practices for working in a VM here (presuming you're in a VM on a Mac as well).
If you're testing within the publish environment and you're still not seeing it, could you also share a copy of the .story file?
Dear Ashley,
I just found out that it only works if I include HTML5 output while publishing, despite the video says its not recomendable.
I also have to run the "story_html5.html" file inside , because the "story.html" doesn't work. ( the output directory contains both )
Im attaching to this post the files and published output directories for both the storyline and engage 13.
Actually its quite an easy process, and if you publish it straight into the articulate online LMS, including the html5, its gonna work.
I hope it helps, because merging storyline with engage 13 creates the most powerfull elearning tool i ever seen.
Fabio
Thanks Fabio for sharing that here - and I see that David recommends not including the HTML5 output for the Engage element, but he doesn't say anything about not including it for the Storyline final publish - so using the story.html or story_html5.html should work either way.
Did the new storyline 2 brought any change on this matter?
Hi Fabio,
Storyline 2 allows you to insert Studio '13 content as described in these tutorials.
Click each link for details.
Microsoft PowerPoint Presentations
Articulate Quizmaker Quizzes
Articulate Engage Interactions
Other Storyline Projects
Hope that helps and please let us know if you need anything else.
Is there any news on allowing Engage 13 interactions to be brought into Storyline 1? I on;y bought Engage 13 as I wanted to use it with my existing Storyline installation and I won't be upgrading to Storyline 2.
Hi Louise,
You won't be able to use the Import Engage functionality to bring it into Storyline 1, but you can use the method here - and it will operate in a similar way as the import does, placing the Engage elements in as a web object.
Has this issue been resolved yet ? I am trying to import an engage interaction (from studio 2013) into storyline.
Hi Kim,
Are you using Storyline 1 or Storyline 2? Storyline 1 still does not have support for importing Studio 13 content, so you may want to investigate a method such as the one here.
If you're using Storyline 2, can you tell us more about the error message you're receiving or what's happening when you try to import the interaction? Please make sure you're following the directions here on how to import Engage into Storyline 2.
Hi,
I have SL2 but wonder if engage importation work ok in it?
I am importing my engages 13 to presenter 13 and from there i am importing the PowerPoint into storyline 2
I want the engages to play in my SL2 course so user can not pass to next slide until the have seem all steps in presentations, Anyone knows how to do that. My engage es setup is Interactive "Show PREV-NEXT Butoons" but it doesn´t work.
As work around i imported the engages to Power(setup the engages in presenter to "Single Item" and "After viewing all steps") and then imported that PowerP into ST2, but l can still click next before the seeing all step in the engage.
Thanks for any help!
Antonio
Hi Antonio,
You should be able to import your Engage interactions into Storyline, and you could also look at following the steps here to import them directly. That article will walk you through the choices in terms of how the next button should function including the specific "next" functionality within Engage. If you've imported them into Presenter first, you'll want to change the next/prev behavior as detailed here.
I have a project originally created in Storyline 1 with Engage '09 interactions from a previous Project. I was disappointed when we upgraded to Studio '13 that the interactions were not compatible. So much so, that we had a computer with Storyline 1 and Studio'09 to edit them easily.
We were told when our group attended the DevLearn convention in November that this issue had been resolved with Storyline 2 and Studio '13. Now I am in the middle of edits and cannot get the "Next Storyline Slide" button to to appear after the completing the Engage interaction.
I have custom buttons throughout the course and do not want to use the player buttons-they are not easy to control, waste too much space, and look odd on screens when they are not being used.
How can I make that button appear?
Hi Alicia,
In the image it looks like it's greyed out and you're unable to select from those options? Is that the behavior you're experiencing? Are you able to share a sample .story file with us that has the Engage interaction embedded? Are you adding the Engage interaction as described here or pulling it in from a Presenter file?
This post was removed by the author
Hi Alicia,
When you reply via email your attachments or embedded images are not included in the forum post. Also the email signature is included, so you'll need to revisit this post if you want to edit it and remove your signature and attach the documents for us to look at.
That’s correct. The options have been greyed out from the beginning. I used the same steps to insert the file as in your link.
The files were original to a presenter file, then imported to Storyline 1. I have since imported the engage files directly into Storyline 2, but the results are the same.
When I am on the inserted Engage slide, I click on the slide and this “Engage Tools” menu comes up. The button I need to control “Next Slide” is greyed out.
Also in the link you sent it talks about editing options, and the controls look grey there too.
Attached is a sampling of the course.
Hi Alicia,
Thanks for sharing your files here and letting us take a look. I was seeing the same behavior myself, so I checked in with some other members of our team and it seems that the show "next slide" button is a legacy feature for Engage '09. Our team has updated the tutorial to reflect that here:
You'll need to utilize the player buttons to allow the user to continue on to the next slide.
That's unfortunate, especially since we were informed differently at the conference. I have no options since I already converted the course to Storyline 2 and now don't have time to redo edits for the interactions in '09.
I don't understand why your products are not compatible with each other. There are numerous posts from unhappy users that experienced the issue initally with the upgrade to Studio '13.
If Storyline 2 has been designed to accept Engage '09 interactions, then why not '13?
At least let me run Studio '09 and '13 on the same machine then. It's a big hassel having to use a separate machine to edit the interactions. :(
Hi Alicia,
My apologies if I was unclear, but Storyline 2 does support Engage '13, but the default behavior is to utilize the same player across both the Engage interaction and the Storyline 2 interface. This was based on feedback that we heard from users, and therefore the option mentioned is greyed out when it's not an Engage 09 interaction. The "next slide" button is still a feature of Engage '09 so the option is left in there if you're also importing an Engage 09 interaction.
It is frustrating and perplexing that Articulate would make their newest product, Storyline 2 compatible with an old version of Studio ('09) and not compatible with the most recent version of Studio ('13). Experienced developers want to maximize the space on the screen and have advanced control over the navigation buttons. The prebuilt navigation buttons waste valuable space on every screen whether being used or not.
Being able to use Engage interactions in a Storyline course allows flexibility in development and the time it takes to develop. I have been able to freshen a Studio '09 course by upgrading it to Storyline and maintaining the Engage interactions originally created. Now I just have 2 sets of buttons. :(
Hi Alicia,
I'm glad you were able to implement a method that would work for you, and Storyline 2 is compatible with both Engage '09 and Engage '13, but since they had different features they'll have slightly different behaviors within the course itself. You're welcome to share your thoughts on this here in the forums or if you would like it to go directly to our product development team you can share your thoughts here.
What is the status of thie? I am trying to convert our old projects form Studio 09 and studio 13 to SL 2 - Please let me know - thansk!
Hi Stan! Both Engage '09 and '13 are compatible with Storyline 2. You can check out how to import those files here.
Leslie -
Thanks for hte quick response! How about how about quiz maker?
Hi Stan! Yes, this should work as well.
Let me elaborate a bit on the Engage that I mentioned above. I'm not sure if you are saying that you have both '09 and '13 files still, but Engage has to be installed and activated to import. Both versions of Engage are probably not installed, so not sure if you need upgrade those files first to the latest version that you are probably utilizing :)
This discussion is closed. You can start a new discussion or contact Articulate Support.