Skip to main content
K
kennetht72107201
Known Participant
April 14, 2017
Answered

Advanced Actions in Cap2017 not saving

  • April 14, 2017
  • 2 replies
  • 1043 views

I'm having an issue with the new release not saving Advanced Actions. When I create and click Save Action, it does not grey out. When I click Close, it tells me to save. When I click Save, it tells me there is already an Action with that name (DUH!). If I don't save (after hitting Save Action the first time), when I reopen the action, it is blank. This is seriously frustrating because I cannot get an action saved in order to use it!!!!! 

This topic has been closed for replies.
Correct answer Lilybiri

What I think is happening is that an image has the same name as a variable. When I changed the name of the image, the action saved and I was able to edit and update with no issues.


May I offer a tip? Decide about a fool-proof naming system. I start each name with 1 or 2 characters identifying the type of item:

  • variables start with v_
  • images start with I_
  • button start with bt_
  • shape button start with SB_
  • smart shape start with SS_

For actions it is less strict for me, for slide events I use EnterSlideLabel.

No doubt that this was the cause of your problems. I had once the same experience when a decision (the Untititled tabs) had the same name as an image, the advanced action was automatically deleted with each update. At that moment I decided about the labeling discipline. There are some exceptions, will not elaborate, but one is very useful: custom states for different objects can have the same name. You can give the same name to an advanced action as the name of the button that will trigger it ​provided​ that you ​first​ label the object, and later the action.

Sorry, but took out the tag 'bug', because this is not a bug. The unique name requirement has nothing to do with a Captivate bug, after all advanced actions are programming using point-and-click.

2 replies

R
rvciv
Participant
April 17, 2017

this is happening to me as well. its infuriating. it's happening in 9 also. its only with actions that were created previously. so if i open a project that already has actions assigned and go to edit them once i go to update the edits the action wont save and then if i exit without saving they erase. meaning i destroy the action. i have worked in Captivate since 5 so i know its not me. it happened as soon as 2017 was released so i upgraded thinking that maybe 9 had been messed up somehow but 2017 is doing it as well. they may need to push an update like they did when 9 first came out. 

Lilybiri
Lilybiri
Legend
April 17, 2017

Did you read the thread completely? As I suspected, for the original question, the origin was dual use of the same name for items.

You are correct that for the first release of 9 upgrading conditional actions had problems, which were quickly solved within two weeks by a patch. I didn't see the same problem with CP2017 until now.  You are talking about upgrading actions? From which version? Can you give some more details, please?

Lilybiri
Lilybiri
Legend
April 14, 2017

I just double-checked (had tested actions extensively in Prerelease, but now checked in final installation) and had no issues whatsoever. Both saving as advanced and as shared action works fine. I used both standard, combinations standard-conditional and while-conditional.

Did you label the action before saving? Can you post a screenshot of the action? Is its name acceptable?

K
kennetht72107201Author
Known Participant
April 14, 2017

I'm not sure what Name Acceptable means but I have other AA's that are named similarly. If I do any kind of edit, it gets deleted. The first image is after I've written the action and saved. The second image is when I reopen to do an edit.savedNewAA reopenNewAA

Lilybiri
Lilybiri
Legend
April 14, 2017

I was asking about the name, because Captivate doesn't accept a name to be used twice, even for a totally different object. Are you sure that the action name, the name of the variable, etc is not used twice? I cannot read the full name of the first decision, but it should also be unique, not used elsewhere.

Has this action been assigned to an event?

As a test, can you try a very simple action, one decision (standard or conditional) to see if you are able to open it?

Those problems are tough, I cannot reproduce your experience, just guessing about possible causes.

I am using a Win10 OS. I have a parallel installation with CP9, both 64-bit. I am running Captivate as Administrator.

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