Skip to main content
jnifferg
Inspiring
March 23, 2016
Answered

Captivate 9 just converted all of my conditional actions to standard actions

  • March 23, 2016
  • 1 reply
  • 581 views

This is not a Captivate 8 conversion issue. I spent several  hours this morning creating conditional actions and assigning them to the learning map that I am creating in Captivate 9. I save the file several times along the way, and also at the end.

I then went to lunch and attended a meeting. When I returned and reopened the file in order to duplicate and edit the existing conditional actions, I found they have been converted to standard actions, and my variable settings and expressions had been dropped.

I do not have a screen shot of what it is supposed to look like -- these are the "Then" actions that were associated with the first condition. The second condition, and all of the "else" statements have been dropped.

I was supposed to have this ready to present to my boss by the end of the day -- and I would have, if I didn't have to start all over. And how do I know this won't happen again?  ARGH!!!!!

HAS ANYONE HAS THIS HAPPEN, AND IS THERE A FIX?

    This topic has been closed for replies.
    Correct answer Lilybiri

    No, they did not install the patch to 9.0.1.320 nor the hotfix to 9.0.0.230. You are still on the first release which had that bug, solved by a hotfix published shortly after the first release. That hotfix is now included in the patch which you need to install ASAP.

    1 reply

    Inspiring
    March 24, 2016

    What version of Cp9 are you using? Have you installed the patch that fixes the issue?

    jnifferg
    jniffergAuthor
    Inspiring
    March 24, 2016

    I am using version 9.0.0.223, This version was installed only 2 weeks ago by my IT group when they gave me a new computer, so I assume any updates and patches would be installed with it.

    Lilybiri
    LilybiriCorrect answer
    Legend
    March 24, 2016

    No, they did not install the patch to 9.0.1.320 nor the hotfix to 9.0.0.230. You are still on the first release which had that bug, solved by a hotfix published shortly after the first release. That hotfix is now included in the patch which you need to install ASAP.