Skip to main content
Known Participant
October 18, 2015
Question

Conditional Actions randomly stop working in CP8

  • October 18, 2015
  • 1 reply
  • 502 views

I've noticed recently that while I've been working on a project in Captivate 8 that some conditional actions randomly stop working or parts of them do.

For example I had a list that displayed what tasks a user had completed throughout the project.

It worked on variables being assigned and then if the variable equalled '1' showing a tick and a description of the task they'd completed.

Like this ...

C Clicked on the image of the TV

While testing it I noticed the page was randomly displaying one of the ticks and the item description even though the variable wasn't equal to '1'. (I'd checked this by putting a text caption with the variable in on the slide, while testing).

I went back and deleted the tab in the conditional action that related to showing those parts of the slide and then created the same tab again in the conditional action.

I re-tested it and it started working.

Does anyone else have experience of Captivate 8 being funny with conditional actions, like how I described?

It's usually the ones that trigger 'on entering a slide' that I tend to find occasionally have to go back and fiddle with. It's not the end of the world but can be annoying especially when all the logic is right and then all of sudden it's not working.

I recently cleared my cache, but would re-installing Captivate 8 help?

This topic has been closed for replies.

1 reply

Lilybiri
Legend
October 18, 2015

I have been creating tons of conditional and advanced actions in all versions of Captivate since 4 (where advanced actions appeared) and never did have the issue you are talking about. Personally when a conditional action is not functioning, I always discover it is due to a human failure in the logic. Because you talk about 'On Enter' event for triggering the action, I hope you are aware of the fact that this event only occurs if you really re-enter the slide, it will not work when you replay the slide with the action. Since many versions it is also possible to make an object visible on another slide than the slide where the action is triggered. Maybe rethinking the actions, and splitting up the one conditional action with many decisions On Enter (which means a lot of evaluating by the system) could help if the published course is deployed with lower bandwidth available to the user?  You don't give details about the number of decisions in the conditional action.

arashmazAuthor
Known Participant
October 19, 2015

Hi Lilybiri‌ thanks for always responding to my questions, I do really appreciate it.

The way I understand 'On Enter' works is on entering the slide it triggers the action. If you navigate away from the slide and then back at a later time it will trigger on entering. Is that right?

The number of decisions the conditional action has is 10, I posted a question earlier on the forum and there were people who responded saying they successfully had up to 35 decisions in one conditional action working. So I've intentionally tried to keep it on the lower side.

One thing I have noticed is the variable which is used to determine whether something shows or is hidden for the one that wasn't working properly shares the name of a smart shape in the project.

I know in a previous post I've seen you mention that variables shouldn't share names with anything else in the project as it can cause Captivate to behave strangely, is that right?

(I do have an example I'll post later with screens)

Thanks

Lilybiri
Legend
October 19, 2015

Indeed, I always insist on keeping each name unique. There are some rare exceptions where you can reuse a name, but on the whole it is a wise decision never to reuse a name. Of course I'm not sure this is the cause of your issues, but it could be. Starting each name with one (or two) character that identifies the object is a way to avoid this: I always start a variable with v_, a shape with S, a shape button with SB etc... Any training I offer for a company will include the creation of a naming table, a discipline to be followed by all trainees.

Yes, that is the way On Enter is working. I just warned that 'Replay a slide' will not have the On Enter action working, as is allowing scrubbing by the user which can result in ending up in the middle of a slide.