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

[Cozmicone]

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.

[Lilybiri · Accepted solution]

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.

[Cozmicone]

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]

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]

These Jive forums are very limited in functionality. Just FYI: shape buttons lose their states when they are used on master slides in Captivate 9 contrary to Captivate 8. For that bug I do not have a workaround, is bothering me a lot more than this conditional action which has a workaround. Shared actions do not suffer from the bug for conditional actions, they are fine.

[Cozmicone]

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.

[Sankaram]

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.

[donalall]

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]

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

already a hotfix released two days ago.

[donalall]

Hi Lieve

My problem relates to conditional actions created in CP9 changing to a standard actions.

One slide project - very basic, responsive, win8.1

I have advanced actions with conditional actions attached to different click boxes - these work ok  (created from a shared action).

But in my advanced action attached to a Smart Shape "Submit" button, all the conditional actions have been converted to standard actions.

So I'm assuming that my issue is a different issue and the Fix won't resolve this.

Any ideas how to resolve? or will i log it as bug?

In the correct answer you mention:

"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."

I can't do this because my conditional actions appear as standard actions.

Regards

Donal.

[Lilybiri]

Hi Donal,

I never did see this behavior at all, and didn't even read anyone complaining about such an issue. This is very weird, because you can imagine that I have already created quite a lot of conditional advanced actions in CP9 (presenting about them next Monday at Learning Summit). The conditional advanced actions in upgraded projects were converted to standard shared actions, not to normal standard actions. That bug has been fixed now.

Before logging as a bug try to find out if you can reproduce the problem in a new project, after having cleared the Preferences folder and the cache.

[donalall]

Hi Lieve,

I cleared Preferences and the cache and created a new responsive project (1 slide) but the problem is still there.

When i created the AA it was working, it was still working when i closed Captivate and reopened it.

I may have restarted the computer as well (I can't remember).

The next day when i opened the project the Submit button conditional actions were converted to standard actions.

Below is my use case.

Captivate 9.0.0.223, Win 8.1

Regards

Donal.

My use case:

Trying to divide a Spanish word into the correct syllables.

Setup

So i have a word and between each letter in the word i have a Line smart shape and a Click box.

Line smart shape has a number of states - Normal, Selected (thicker line), Correct (thicker green line), Incorrect (thicker red line).

There is a basic smart shape "Submit" button.

Click box AA

Each click box has AA that sets:

• the Line smart shape state to Normal or Selected
• "v_Line01" to 0 (unselected) or 1 (selected)

This AA works.

Submit AA

(the problem is with this AA - the conditional actions are convered to Standard actions.)

On the Submit button i have a AA that checks if Line smart shape is:

• selected (v_Line01 = 1) AND
• one of the answers

If it IS:

• change state of Line smart shape to Correct (thicker green line)
• add 1 to v_CorrectAnswer

If it IS NOT:

• change state of Line smart shape to Incorrect (thicker red line)
• add 1 to v_IncorrectAnswer

In the new project i just tested the first Line smart shape.

[mohanadas]

Hi Donal.

If possible could you share the project where you are facing the issue, with the original conditional action? This will help us to investigate this at our end.

You can upload it to a shared location (eg Dropbox) and send the link to mdas@adobe.com

Thanks,

Mohana

[donalall]

Hi Mohana,

I created a new project to send to you and everything worked ok - the conditional actions stayed as conditional actions.

So not sure why it was not working previously?

I have reinstalled Captivate (9.0.0.223) and if i experience the issue again i will let you know.

Regards

Donal.

[jamesd35190521]

Pre-hot fix: All of my cp9 projects which were based on cp7 projects had this issue.

Post-hot fix: The issue remained for all previously saved, converted, projects. To apply the fix, I just re-opened a copy of the original (unconverted) cp7 project in cp9, copied the slides I needed and pasted it in the cp9 project. All is working fine.

[piotr.burchart]

Hi,

Hi,

I have exactly the same problem with my project.

Even within new project(s) created from scratch all conditional actions has been converted into standard actions. This is very annoying because I have redo all actions from the beginning again and again each time I will open project to make some changes.

Peter

[Lilybiri]

Please, install the hotfix. It was released soon after the discovery of this bug (conditional actions are converted to standard shared actions):

Hot fix | Adobe Captivate 9 issues

Version number should become 9.0.0.230

[piotr.burchart]

Hi,

First of all: my problem relates to conditional actions created in CP9 changing to a standard actions (this is project created in CP9)

Second: I already installed the hot fix.

This is same problem like in Donal's post (see above -  26/September)

Thank you for your respond.

Peter

[Lilybiri]

I was talking about Captivate 9, I have been creating many, many conditional advanced actions after installing the hotfix. That hot fix will NOT repair already created actions. Sorry they were converted to shared actions as you can see from all the screenshots posted above: you see the typical dropdown lists that appear with shared actions presented as templates in the Advanced Actions dialog box.

BTW Donal reported on 19 september that it was fixed.

[piotr.burchart]

Hi,

I have created many conditional actions as well . The problem with conditional actions accrued in project created in Captivate 9 from scratch - NEW PROJECT!. All conditional actions, (also problem is with share actions because I've crated them based on the above conditional broken actions).

To clarify: project created in CP9, all conditional actions has been converted to standard actions.

2nd: there is also few other bugs: unable to send forward or backward objects with different states (will send print screen soon); unable to change position on screen objects with states (send screenshots soon as well).

So, my question is: should I report the above bugs right now or you are aware of the above issues and I should wait for appropriate hot fix (upgrades) soon?

Thank you for your replay.

Piotr

[Lilybiri]

Maybe you misunderstand: I am not working for Adobe, I'm just a user like you.

After installing the hot fix, the problem with conditional actions being converted to standard shared actions is gone totally for me, both for upgraded projects and for new projects created from scratch in CP9. That is the reason I have insisted on asking if you did install the hotfix (correctly) and have now version 9.0.0.230? I got the same answer from many other users on this forum (bug fixed with conditional actions), seems like something has gone wrong with your installation of the hotfix.

The issues with states are still there and have been reported many times, at least for states not following when moving objects on the stage.  I don't understand what you really mean by 'sending objects forward or backward with different states). I suspect the team is working to solve those issues and to release a patch (different from a hotfix).