Storyline 360 Drag'n Drop Bug Correct Layer Incorrect Layer

Hi, 

I have a normal Drag'n Drop (Freeform). 

(for example 2 items on 1 target - both must be dropped)

When i drop the correct items on the target and klick submit, Storyline shows the "Correct Layer". That works fine. If i revisit the same Drag'n Drop and drop only the first item and click submit it also shows the correct layer. And thats the problem, normally it should show the incorrect layer. 

I tried multiple thinks. The Slide is on "reset to initial state". I also tried multible attemps.

Can someone look at my file and help me?

I Add an attachment. 

We are using Storyline 360 update 3.7 and 3.8. Both version have the same problem.

 

thanks :)

Sam

2 Replies
Ashley Terwilliger-Pollard

Hi Sam, 

Thanks for reaching out here. I tested your file and a brand new file, so I've reported it to my team as a possible software bug. 

From here, I’ll meet with my team to take a closer look so we can determine next steps. Sometimes my team catches errors in my logic and we don’t have a bug after all. Of course, if that’s the case, I’ll let you know! 

Depending on priority and risk, some bugs can be fixed quickly, while others take longer to resolve. Here's more information on how we identify and tackle bugs.

I’ll let you know as soon as we have an update on this issue. Thanks so much again for letting us know about this, and I’m sorry if it’s slowing you down.

 

Ashley Terwilliger-Pollard

Hi all,

Great news!  We just released another update for Articulate 360, and included a few important fixes and new features that you'll see in the release notes here.  

The item you'll be interested in is how it fixed the issue where freeform drag-and-drop questions could be marked correct on the second attempt in HTML5 output even when learners answered incorrectly.

Just launch the Articulate 360 desktop app on your computer and click the Update button for each application. Details here.

Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.