Issue with inserted Engage 360's Conversation into Storyline when viewing on Review

* side note, my instructions do say to click the person to continue the conversation, I had assumed that I could add hotspots or interactions and triggers, but I couldn't get that to work, and this was just a test project file

Hey Kyle - I did a brief test and I'm not seeing that behavior when re-visiting my lightbox slide.

Would you be able to share your .story file for us to take a peek?

Thanks for getting back to me.

Your example worked perfectly! Nice to see.

Something must be wrong with my setup. This is nice to know, because I was creating one from scratch which is kinda hard with the need for the scroll bar.

I'm attaching my .story file now.

Thanks,
Kyle

I just published "Web" and viewed in the Chrome Browser.  It's doing the same thing, so I'm convinced I have done something wrong.

It also has a new issue. I tried making a change and then publish to Review and after 10 minutes it says that it is still processing.  Older versions are showing up. I published as a new version and then tried publishing as a new course.

Details:
I'm publishing with Flash/HTML

Leslie, could you do me a favor and send me the test file you made?

This is not working for me after I tried new files - it does the same thing.

It happens in the lightbox, and it happens if I visit the single slide.
If I've viewed the lightbox and closed it, then both will show the last item, and when I use the PREV button, it will go backwards and only show one at a time instead of having all of the conversations and going backwards eliminating just 1 while others stay on screen.

This engage file is previewing fine in the ENGAGE software, so I thought this was going to work and I only wasted 2 hours with it, so I may need to return to the custom version if this is an issue that can't be fixed.

Thanks,
Kyle

FYI, IT's doing it with HTML/FLASH too. and the FLASH/HTML

I'm very confused how it could work for you and not me.

Thanks,

Yes, I can share what I worked on. I have not gotten back to testing your file.

Thank you very much!

I think I'll open a support ticket.  My team already started producing scenarios with the Engage Interaction, so I hope they can figure it out, if you see the issues with my file too and without answers.

THanks,

Kyle

Hi Kyle,

Do you have a case number for your Support instance? I just wanted to connect it to the work you've done here too so that our team isn't starting from scratch with you! 

Hey Kyle - In addition, I took a look at the file you've shared here and it looks to be set up in a more non-traditional way with the 'click' to see conversation. If you could share the .intr file with our team as well, that would certainly be helpful.

I was wanting the lightbox with the interaction to appear after the user clicked something on the stage.  I know your brief example used the next button from the interface instead of clicking on something on the stage.

Is the next button the only traditional way of doing it or are there other ways to trigger the lightbox that might be okay, like using the timeline reaches cue points or timeline ends/starts? 

I will attach the Engage file here too.  I didn't end up logging a support ticket yet.

This brings up a question I have.... I'm very new to using ENGAGE myself, but...
My co-worker told me that I wouldn't really need the Engage files once they are in Storyline.  He said that in the past he has duplicated slides in Storyline that have an ENGAGE interaction (not the conversation interaction) and he had 5 slides that all had different content from him using the Edit With Engage in the Storyline Format tab. (Then Save and Close).  

Is this a bad practice?
Should we keep an engage file for each of 5 similar interactions that have different content?

 This is not what I did, but I don't want that to cause issues like what I'm having (later on in our project), but it seemed to publish fine for him.

Hey Kyle - Using an object should be fine. I adjusted my file to include this as well.

Your co-worker is correct, Storyline can do much of what is within Engage as well. It's your choice in how you'd want to build it though. If you find the Engage templates easier, that's perfectly fine.

I am still not sure why your file displayed the behavior that it did. I adjusted my file and added your Engage file shared here and it works perfectly.

File attached and here is the published output.

Thanks for following up!

That must prove that it's an issue with that Storyline file. But the bug has infested into are production files due tomorrow . I got a grace period till Monday though, so I'll have to revert to a custom version I created and shared with This Hero community.

The NEW issue is is worse!!! It's happening with a production ready course that has 5 engage interactions . my co-worker and I took a finished Storyboard that was completed in Storyline and split it up to have me work on the first half while he took the second half.

i was first having the issues in my testing file that I sent you, and my half has 1 of those engage interactions with issues you've already seen.

now we published his half with 3 engage interactions and his is behaving worse.

its set to automatically play (appears in a light box from clicking a true built in button this time. 

When we see it, the screen is empty (white stage / no graphics.) with the previous next button showing.  We click next and nothing happened, then I rolled over the stage area and the white went away, but it revealed the 2nd speech bubble, not the first. I hit previous and it showed just the first speech bubble. I moved the mouse around and the white came back (turns out that the correct graphics only show while rolled over the stage with mouse and if mouse is off stage it goes back to all white.) it toggles back and forth.

This is his file.

so his user experience is fully broken, mine kinda worked but is always broken when returning to review.

this is happening with the regular slide too. Not just when lightboxed.

the project was due tomorrow , and I didn't use support tickets because you proved it worked, and I sadly assumed it was a bug with the Engage file.  (You have helped narrow down the issue, thanks!) I had made a fresh new engage file and a new Storyline file from scratch - and that worked. Our files don't like engage :(

I'm surprised no one else has reported this issue.

im not upset, I understand that all software will have bugs.

im just hoping the community might be able to help.- 

thanks again Leslie,

- Kyle

Hi Kyle!

Sorry we haven't been able to figure out the root cause in your file and since Leslie's version worked, it's even more mysterious! Something you wrote though caused me a bit of pause...

When you and your colleague are splitting up and sharing the file to work on it, are you following the steps here for collaborative workflows? That could be a root cause if the files aren't being saved and edited locally and contributing to overall oddities in the files. Just one idea as you dig a bit deeper into this issue! 

I'm glad the new ones worked and sorry that you'll have to work through the weekend on these. Keep us posted if you're able to figure out anything else that could have caused it!

That is all great advice, but the file I attached was actually a testing file that was never part of a project.  I wanted to make sure the whole set-up would work before having our team put this into our project files. Somehow the issue happened again in our project files that were never part of our test files, but they ended up having the way worse issue of showing only white on the stage until the mouse hovered over the stage.  So 2 separate Storyline files are having the issues. I can't share the project with the same and additional issues but I'm stumped.  Tom Kuhlmann actually shared an example of a custom solution that was better than my custom solution. It's more time, but pretty cool.

Once I thought I was in the clear, we then split up the project and we have had to follow those steps for a decade because of learning the hard way when using Flash from Adobe in the past. (They say that their software is not supported for working off of a network) It works, but it can easily lead to corrupt files.  I had lost hours of work and won't let myself loose more than a couple minutes of work.  I always work on the desktop and then upload to the server after closing out the program. I get annoyed that I save so much and always save up a version (I usually get into the hundreds when increasing the version number by 1 at the end of the file names.)

Here is my custom solution: https://360.articulate.com/review/content/49cd51c2-1e99-4837-a760-b2695a73c487/review 

Here is Tom's better custom solution: https://360.articulate.com/review/content/e624a00a-02e3-4f4c-8fe0-0f42cb2a8fc2/review  

Worth a try! But glad you got a cool solution from Tom too. 

It's so Odd, I'm back to the issues with a single Engage file from a brand new test file with just one button on a slide and then the other slide holds the engage file and opens on the first slide in a light box.

https://360.articulate.com/review/content/2333ba3c-b7ef-4f3a-bf01-dc258ceb9625/review

We still want this solution, its quicker and easier for our IDs that have the TEAM 360 and could just send me (the developer) a finished Engage file, it was quick to teach them.

I just edited my past and added the attachment of the 2 slide Storyline file.