Forum Discussion

tati_shoj's avatar
tati_shoj
New to the Community
14 hours ago

Slide-level scrub control after first view (without affecting checkpoints?)

Hi everyone,

I’m running into a navigation issue in Storyline and wanted to see if there’s a workaround I might be missing.

Right now, I have the player set so learners can’t scrub until a slide has been fully viewed. This works fine for standard content slides, but I’m running into issues with checkpoint slides that are set to “Reset to initial state” so learners can retry them.

Because those checkpoint slides never register as “completed,” if a learner clicks Previous to revisit them, the Previous/Continue buttons (and scrubbing) stop responding, even though they appear active.

If I allow scrubbing at the project level, everything works fine, but I’m trying to avoid enabling scrubbing globally.

My question:
Is there a way to control scrubbing at the slide level (for example, allow scrubbing after the first view on video/content slides only), without impacting checkpoint slides?

Or alternatively, is there a best practice for handling navigation when using “Reset to initial state” on checkpoint slides in combination with restricted scrubbing?

Would love to know how others are handling this scenario. Thanks in advance!

1 Reply

  • Frankie's avatar
    Frankie
    Community Member
    11 hours ago

    Hi tati_shoj,

    From what I'm understanding, you have your Player Properties > Player Controls set to this:

    And you run into issues with your project because your Slide Properties on these "checkpoint" slides are set to this:

    And when a learner revisits those slides that are set to "Reset to initial state" you run into navigation issues because the logic treats that slide as not completed. 

    Is there a way to control seekbar dragging at a slide-level?

    No.

    Is there a best practice or alternative solution?

    Yes. Here are some ideas I might try. They are more of a patch and might not be the most ideal workarounds but they're worth a shot.

    • Try a "resume saved state"  along with a "retry" button that the user can click to manually restart the slide.

     

    or

     

    • Create a hidden duplicate slide that can only be visited if the user clicks the previous button on the next slide.
    Default previous button behavior trigger.Updated previous button behavior that goes directly to the duplicate "non-progress-tracking" version of your slide in question.

    Hope some or all of this helps!

    ~ Frankie