In this segment from my last live stream, I show you how to find and delete unused advanced actions from your Adobe Captivate eLearning project.
Not useful at all. I already knew this. The problem is that Captivate will deny deletion of an action, saying it is in use. However, clicking the Usage buttons reveals that it’s actually not in use. The same thing happens with variables. Captivate will claim that a certain variable is in use by an advanced action when it’s actually not. If you could help me fix this @
Very useful !
Great! Thanks a lot.
Quite unusable. There are buttons to clean library and variables, they forgot this one.
Interesting how the program doesn’t have a button for “unused advanced actions”.
Thank you! Very helpful.
Can we please have a more efficient method for removing unused variables and advanced actions? Let it break if we ignore warnings of deleting related elements and logic. Plus, Captivate holding onto certain advanced actions. This has been an issue for years. Should not have to start from scratch to break the connection to unused elements. Known bug, please find a solution.
Almost all the people on the community site are fellow users like yourself. Please submit your feature requests and bug reports to Adobe through the reporting features available on this site.
Hi, is there any way of deleting multiple unused advanced actions from the project, rather than one by one?
It’s also a good idea to document (bleh, I know!) the purpose of the Advance Action. Use the description fields to describe to yourself, your team members, or the NEXT developer.
Yes, I agree. I often am the designer and the developer so I’ve picked up the bad habit of not detailing those sorts of things. Certainly, if you work within a team of many developers it’s a great best practice.
You must be logged in to post a comment.
