Skip to main content
C
Cozmicone
Inspiring
September 4, 2015
Answered

Why/how did CP9 convert all my conditional actions to standard actions?

  • September 4, 2015
  • 4 replies
  • 1758 views

I have a CP8 project I've been working on for a few months now and finally upgraded to CP9. I realized right away that any of my smart shape buttons using rollover states didn't have the rollover state carry over from 8 to 9, so I saved a copy of the file in CP9 so I could have both versions open side-by-side so I could go back into the CP8 file to see how I setup the rollover states so I could rebuild them in 9. That really isn't a big deal, but I'm finding that every one of my advanced actions have been converted to a standard action.

This is a preview of one action in CP8:

And this is how it now appears in CP9

Everything else in the file, with the exception of smart shape buttons with rollover states, is intact as far as I can tell. What I'm confounded by is why/how every conditional action was converted to a standard action. From what I can see, everything inside the IF and ELSE statements were purged and everything under the Actions across all decisions were combined together along with any action referencing a variable being disconnected from the variable.

Fortunately I didn't do a whole lot of work on the file so I can re-open and re-save the CP8 file again, but this is just a super weird glitch.

    This topic has been closed for replies.
    Correct answer Lilybiri

    It is a known bug, already mentioned in this forum right after the release. A patch is promised ASAP to fix it.

    Workaround: do a small editing of the conditional action, so that you can use the Update action button. When saving the actions will remain conditional. BTW they are not converted to a standard advanced action but to a shared standard action.

    4 replies

    Sankaram
    Adobe Employee
    Sankaram
    Adobe Employee
    September 25, 2015

    Hi,

        We have published Captivate 9 hot fix for the issue. KB article @ https://helpx.adobe.com/captivate/kb/hot-fix-captivate-9.html

    Thanks,

    Sankaram.

      D
      donalall
      Inspiring
      September 26, 2015

      Hi

      Is this bug related to conditional actions in projects that have been upgraded to CP9?

      Or does the bug include conditional actions created in CP9 that are now appearing as standard actions?

      Regards

      Donal.

      Lilybiri
      Lilybiri
      Legend
      September 26, 2015

      Only for upgraded conditional actions, not for the shared actions. There is

      already a hotfix released two days ago.

      C
      CozmiconeAuthor
      Inspiring
      September 6, 2015

      Thanks for the feedback.

      Per the shape buttons, not all of them lost their states. Most of them did but some of them did not. It's weird how it just wasn't all of them.

      C
      CozmiconeAuthor
      Inspiring
      September 4, 2015

      Well that stinks regarding the bug. It would be nice if that was stickied to the top of these forums so people could easily find it. It's especially troubling since this problem isn't mentioned in the Top Issues post here, Top issues | Adobe Captivate 9

      RodWard
      Community Expert
      RodWardCommunity Expert
      Community Expert
      September 5, 2015

      Don't use those lists of "top issues" that Adobe publishes as a guide for how many issues you may encounter when using Captivate.

      There are potentially hundreds of issues, which is why my e-books on Troubleshooting Adobe Captivate wouldn't be so long.  (The one I'm currently updating for Cp8/9 is now over 350 pages.)

      And Captivate (like all other software apps) always has its share of annoying bugs. Fortunately, as Lieve mentions above, this particular bug at least has a workaround solution.  Be grateful.  Many others are not so lucky.

        Lilybiri
        LilybiriCorrect answer
        Legend
        September 4, 2015

        It is a known bug, already mentioned in this forum right after the release. A patch is promised ASAP to fix it.

        Workaround: do a small editing of the conditional action, so that you can use the Update action button. When saving the actions will remain conditional. BTW they are not converted to a standard advanced action but to a shared standard action.

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices