Drag and Drop target not working
Hello all. I am building a freeform question that is PICK ONE, but it has drag n drop elements included. For the example shared, the correct answer is indicated by the hotspot targets (2 on the right). But I need the learner to be able to drop the red and black probes on the 2 on the left (incorrect). When I test, the probe is dropped in a strange location on the slide. Currently the correct targets work as expected.... it's the wrong targets that are killing me right now. I have tried manipulating the drop target (blue box), but to no avail. This is not my original project; I am adapting it from the original author. I have tried everything I can think of but I am stuck. I appreciate any help the community can provide. FYI... this is 1 of 3 questions I am building.Bug: learner_response shows underscores for Non-Latin Languages in LMS Tracking for Survey Question
Hi Team, I have encountered an issue with Survey Questions in Storyline 360 (Version 3.109) when publishing to SCORM 2004 (3rd Edition). When a learner answers Survey Pick One, Pick Many, or Short Answer questions in non-Latin languages such as Russian, Chinese, Japanese, Korean, Thai, or Arabic, the "cmi.interactions.n.learner_response" value is stored as underscores (__________) instead of the actual response text in the SCORM Cloud LMS. Here is attached screenshot for the reference. Please find the attached screenshot for reference. However, the "cmi.interactions.n.description" field correctly stores the localized text, indicating that the LMS and SCORM Cloud support Unicode characters. Expected Behavior: The learner_response field should display the selected response in the original language instead of underscores. Could you please confirm whether this is a known issue or limitation in Storyline 360? If so, is there a recommended workaround or fix?JavaScript Help - Object Variables
Hey All! I learned how to do a few JavaScript animations from a YouTube video. It was a couple of years ago before Storyline put in their object reference code. The video I learned from uses the Accessibility box to call the object. It works great, but if I have someone that is disabled, the Accessibility text on my flip card is now "card_back" instead of an actual description. I am trying to figure out how to change my code to read the object reference instead of the accessibility box. Hope that makes sense... Here is my current code that works with the accessibility box call: //select the Card(s) var card_front = document.querySelector("[data-acc-text='card_front']"); var card_back = document.querySelector("[data-acc-text='card_back']"); //Card Front Timeline let card_front_timeline = gsap.timeline(); card_front_timeline.set(card_back,{rotateY:-90}); card_front_timeline.to(card_front,{rotateY:-90, duration:0.5}); card_front_timeline.to(card_back,{rotateY:0, duration:0.5}); How do I chance the //select the card(s) section to the Storyline object references? Here are the two that I am trying to use: const cardFront = object('64XQyHVDBOj'); const cardBack = object('6ft6OP0e9xE'); Any help would be greatly appreciated! And please let me know if something is unclear.Can the AI Assistant implement character limits in CC segments?
Hello, Articulate community! Just wondering if the Storyline or Rise AI Assistant can implement character limits in CC segments. Our team abides by DCMP guidelines, which advise no more than 32 characters (including spaces) and a max of two lines per segment. I haven't tried asking the AI Assistant this myself, but if this capability exists in Storyline and/or Rise, can anyone recommend an effective prompt to use to achieve these results? If this feature doesn't yet exist, could I submit a feature request for future versions of SL and Rise? Thanks much in advance. :)Slide names turning into "Intro Slide" in Review 360
Hi all, I’m seeing a weird issue where some slide names show correctly in Storyline (scene + player menu), but after publishing to Review 360, they turn into "Intro Slide". I’ve tried renaming slides and resetting the player menu, but no luck. Is this a known issue or a bug? Any ideas? Thanks!Prevent Forward Seeking but Allow Backward Navigation in Video (Storyline .story Template Request)
Hi everyone, I’m working with Articulate Storyline to build video-based e-learning modules (SCORM for LMS/Moodle), and I’m trying to implement a very specific navigation behavior. Goal: The learner cannot skip forward in the video timeline (video in unique in slide) The learner can go backward (rewind) at any time Ideally, the restriction works progressively (i.e., they can only move within the portion already viewed) I know there are workarounds using: cue points variables (e.g., tracking max progress) triggers to block forward seeking However, I’m looking for a ready-to-use .story template (or a solid implementation example) that achieves this reliably, especially in SCORM environments. If anyone has already built something like this and is willing to share a .story file or outline the trigger logic, I’d really appreciate it. Thanks in advance!Combine CC in Closed Caption Editor
Wouldn't it be amazing if there were a function in the Closed Captions Editor that let you just click to say "Combine with Previous" or "Combine with Next"? This will save so much time when the AI-generated CCs are too short, and at the moment, you have to manually add that CC to the next or previous one. Camtasia from TechSmith has this feature, and I cannot tell you how much I miss that feature here in the beloved Articulate Rise or Storyline. Especially because of WCAG regulations.
