Inspiring

Question

Captivate 9 converts CP8 Conditional Advanced Actions to Standard Actions, Not Good :(

Forum|Forum|10 years ago
August 24, 2015
6 replies
2774 views

Okay, I've just posted a CP8 to CP9 project conversion issue in another post thinking that I would add any other bugs I find there, but this could be a MAJOR problem if you want to take your previous projects to CP9 and so decided to create a new post just for this issue. Again, I would be happy if there is a work around or if I'm the only one experiencing this but if not then this is a bit of show stopper upgrading any projects I have to CP9.

Can someone please try this and let me know if they get the same result.

1. Open a project from Captivate 8 or earlier (I've only tried CP8) which uses Conditional Advanced Actions in CP9.

2. Check that all your Conditional Advanced Actions are working correctly

3. Save your project as a CP9 file

4. Close the file down and then open it again in CP9

5. Check to see if your Conditional Advanced Actions are still working.

In my case, I found that when I re-opened my project as a CP9 file, all Conditional Advanced Actions had been converted to Standard Actions. Basically this has screwed my project!

Please let me know if you encounter the same issue or not.

AndyK

This topic has been closed for replies.

Sankaram

Adobe Employee

Hi,

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

Thanks,

Sankaram.

Andy_K_nzAuthor

Inspiring

Hi Sankaram.

Thanks for posting the fix

AndyK

momarishere

Participating Frequently

I see your point, RodWard, and I am sure I am not alone with other humans that have overlooked something in the past. It's our nature. Coming from a software development company though, you don't release software that is buggy and that is what I meant by my previous post. Ideally, you'd have a list of features that become release blockers and you had better check everything off that list before you release (else, as Andy mentions, you lose ground to competitors).

I've been around since Captivate 3 and a lurker on the forums for quite some time. This is the first time I've chimed in about any bugs I've found and I probably should have jumped in sooner. This one cost me days of work to fix, since I made updates to several projects after the update. This version has some pretty cool features and thankfully most of them work.

Don't get me wrong: I love using Captivate and I am usually the first one here to sing its praises. I just disagree with the way these bugs are typically played down.

RodWard

Community Expert

My take on the software industry is a little different, and YES I have worked in software companies too.

For better or worse, what I'm seeing in the software industry right now is that more and more companies see getting the product out there on the market with as many new features as possible as their BEST marketing strategy. They see this as the "necessity", while having that product be absolutely bug-free is a "nice to have".

Captivate is far and away a more powerful and complex product than its nearest competitor Articulate Storyline, which also has some bugs. I've used every Captivate version since it first came out and most of them had some glaring bug. I don't approve of this, but I think Adobe (like most other large software companies) has done the numbers and realised that people like us still buy the new version based primarily on all the marketing blurb and NOT on some guarantee that it will never fail you in any way.

No company likes to be publicly embarrassed. So of course Adobe has quality control/assurance or whatever the Test department is now called. But I'd bet my house that those people don't build e-learning courses for a living. They are likely lowly paid drones that are following test scripts that were written by the software architects/designers (...who are ALSO not people that build e-learning courses for a living). It's a safe bet that Captivate 9 wasn't released until ALL those test scripts were passed. But my guess is that there just didn't happen to be a test script in the mix that was supposed to specifically check what happened to a Captivate 8 project's Conditional Actions when it got upgraded. They were probably only checking that conditional actions worked. If there WAS such a script and the tester missed it, then that person probably has a sore backside right now (if they still have a job). But I still believe this to be just simple case of human error.

momarishere

Participating Frequently

Oh I did, and thanks for the workaround, Andy. However, this seems to be a recurring theme for Adobe. Very quick to release yet there always seems to be a catch...in my eyes this is a huge bug, as we use advanced actions quite a bit. Beyond the fact that it converts conditional actions to standard actions, the user variables specified in standard actions are also just removed. This is costing a lot of time to work around.

Lilybiri

Legend

They are converted to shared actions. Shared conditional actions don't have

that upgrade issue.

momarishere

Participating Frequently

I am experiencing the same issue. Ugh! Please let us know when there is a fix.

M

met547

Inspiring

Try Andy's work around, works like a charm. Thanks Andy!

Andy_K_nzAuthor

Inspiring

So I've done more testing and found a work around, but I don't like it.

I've created some simple CP8 projects with conditional actions, then opened them and saved them as CP9 and got the same result. However, I've found that if I updated the conditional action in CP9 before I save the project Captivate remembers that this action is conditional. The problem is that I have projects with many many many conditional actions and this will be a time consuming process to modify every conditional action in a project if I want to upgrade a project to CP9. Put simply....Gurrrrrrrrrrrrrrr

Let me know if you get the same results.

AndyK

RodWard

Community Expert

I can confirm that I get the same results when creating a new file in Cp8 then adding a Conditional Action and later opening and saving in Cp9.

Fortunately, (for me) I usually start all of my projects from a CPTX template starter file that I've been migrating from version to version for years now. Conditional Actions in those projects are unaffected by this new bug. But it DOES occur with any file created from scratch in Cp8.

I can see how this would be a major bummer for anyone trying to upgrade files at present. I generally recommend that whenever you migrate files you use SAVE AS and add a suffix that indicates the Cp version number (e.g. MyFile_Cp8.cptx, MyFile_Cp9.cptx). That would appear to be a sound thing to do in this case as well. That way, if you screw up, you can always go back to the Cp8 version and start again to make sure you don't lose all of your Conditional Actions.

Andy_K_nzAuthor

Inspiring

‌Hi Rod,

Thanks for checking that out for me and assuring me that it is not just my system creating the issue. You are absolutely right in advising to always use the SAVE AS option when migrating a project to a new version, which I did do btw. I may have been a little dramatic when I said my project was screwed. What I really meant is that I initially thought that I would not be able to upgrade these projects to CP9, but it looks like I can via the work around above. I'm just disappointed that it will not be a simple process. I hope that a patch is released that will fix this bug.

AndyK

nsukumar

Adobe Employee

Hi Andy,

Can you please share the Cp8 project with us so that we can investigate the issue at our end. Please upload it to a shared workspace(Say Dropbox), Send me the link at nsukumar@adobe.com

Thanks,

Nimmy Sukumaran.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded