Skip to main content
matt_creating
Known Participant
January 29, 2017
Question

Deciphering Advanced Actions

  • January 29, 2017
  • 1 reply
  • 187 views

Hello Community,

I need a little assistance deciphering some advanced actions.  I'm updating a project that was originally completed in Cap7.  They've asked me to fix some lag issues that were happening on their knowledge check slides (caused by some timeline problems which I fixed without issue) and fix a bookmarking issue that causing no bookmark to be set if the participant didn't exit the course properly.  I'm doing this in Cap9The courses are being run from a mySQL database that courses communicate with via Javascript (this part is a little beyond me, ok a lot beyond me).  I think I took care of the bookmarking issue without a problem on the first course by assigning the previously programmed "SetBookmark" advanced action the original developer employed to the "On Exit" function of each slide.  I still need to test this in the deployed environment, but I think I got that one.

The problem I now have is that I've gotten to the second of the two courses that I supposed to update and the setup is different.  Now there are advanced actions applied to each slide "On Enter" and "On Exit."  I have a general idea of what their function is but I'm not sure what their exact implication are.  Can someone help me out with the effects of these AAs and let me know I how I might be able to adjust them so that if someone exits the course unexpectedly their progress is saved?

Here are some screen shots:

Any assistance is really appreciated

This topic has been closed for replies.

1 reply

Lilybiri
Legend
January 29, 2017

It is never a good idea to use On Exit event of slides.  That event is not really to be trusted and only occurs if the last frame of a slide is really visited which is not always the case. I see a Next button which will probably jump over the last frames of a slide, but that is only one example. The action is executed after visit to the last slide, which is probably the reason of that setup in the standard action, where the playhead is rewind one slide.The ideas of micronavigation are used, hence the use of the Expression, the system var cpCmndGotoFrame. But why a Pause is used, while an advanced action by default is pausing the slide is another mystery.

Have a look at: Events and (advanced) Actions - Captivate blog

Micro-Navigation in Adobe Captivate - Captivate blog

You seem to be unaware of the Preview feature of a conditional advanced action: use the first button on the top control bar (arrow, looks like a play button) to show the complete action, becaue in your screenshots you only show the THEN, not the ELSE part of the conditioal action.

Probably some user variables are stored, using cookies (for SWF) or local storage (for HTML) but that is not clear in your story. The meaning of the user variable v_stoppedAt? I suppose it is a slide number, not a frame number.