Advanced actions multiply when using Project template (Captivate 2019)

[AAutomation]

Hi all, I have a problem with advanced actions in .cptx files created from .cptl (template) file.

I have a project template (.cptl) file, which has some slides, advanced actions and variables defined, so that I don't need to create them every time I create a new project. Two kinds of problems occur when I create a new .cptx file from the template (File > New Project > Project from Template):

1. Even though I remove extra slides, advanced actions & variables used on those slide still "haunt" my advanced actions list, and I can't remove them. If I try to remove them, Captivate says they are in use. When I click "Usage", I see this:

So, the action is used on some "Project template" slide - the corresponding slide has been removed from the actual project. What is this? How can I remove these advanced actions that are not in use?

2. Some of my advanced actions (in this case an "On Exit" action) and corresponding variables multiply like little bunnies. This is an action that has been used on almost every slide on the template. When I click open the action, there is nothing in it (it doesn't even show the action name when it is opened even though it is visible on the list) and I can't remove it:

I tried to look for a solution for removing unwanted and unused advanced actions from a project from the community, but haven't found no solution. I also haven't found a solution to remove multiple unused advanced actions, it seems that the only way to remove multiple actions is one-by-one.

[Lilybiri]

Since multiple versions the use of cptl files is very biuggy when they include advanced actions and variables. I have tried to warn about that whenever possible, but it would be better if the cptl-files had been taken out since long. Duplication of varialbes, advanced actions turning crazy, all recognisable to me. I have not used any cptl file since version 7 (we are at 11.5) when those problems started.

For design reasons a theme would be sufficient to replace a template. . Personally I always use shared actions when possible to replace advanced actions because they are not only more flexible, but also do not cause the same problems. it is a breeze to delete unused shared actions since they are in the project Library. Storing much used shared actions and variables in a dedicated project library makes it so easy to reuse them in any project since you can open it as external Library besides the Project library.  

I am sorry not to be able to help you to fix the present situation. Curse me if you want, I am used to that in this forum. Just took this opportunity again to warn agains using cptl-files and explain some reasons.

Indeed, you need to delete each advanced action individually, if you succeed at doing it. The list with advanced actions is moreover one of the rare lists where filtering is impossible which makes it even tougher.

If you need something like a 'template' it is is safer to use a cptx-file which you can lock in the OS, so that using it means making a copy of that file to avoid deleting the original cptx-file.

Deleting an advanced action is a pain in...  You need first to cut all attachments to events, whichis often forgotten. Moreover you can never reuse the name of an advanced action even if you are able to delete it. Not the case for shared actions.

[AAutomation]

Thank you, Lilybiri.

I think I have read something about the buggy cptl files before, but I did not fully realize what kind of problems they might cause. I heed your warning, perhaps it is best for me as well to change my template to cptx file and start using Themes and shared actions. I will not curse you, this is solid advice. 

You mention "locking the cptx file in the OS" - how can I dothis? Is there a another post or some instructions about it somewhere else?

[Lilybiri]

I didn't specify how to lock the file because I was not sure about the OS you are using. On Windows that can be done in the Explorer with the right-click menu. Choose the option 'Read only'. 

[AAutomation]

Thank you Lilybiri! I'm using Windows. I will try that "locking" as you instructed!

[RodWard]

I found this issue back when Cp7 was the current version and blogged about it here:

https://www.infosemantics.com.au/duplication-issues-in-adobe-captivate-cptl-templates/

Sad to say Adobe hasn't fixed the issue and that's why we have had to warn Captivate users against using CPTL templates ever since.

We're sorry that you've run into this issue, but this one is well and truly owned by the Adobe Captivate development team. They've had plenty of versions to fix this and instead just added other stuff hardly anyone uses instead. 

Please log a bug report about it.

[AAutomation]

Hi RodWard,

thank you for the link, I will check it. I will also log a bug report.

It really baffles me, though, that if you have something called "template file", then you can't actually use it as template because it does not work like it's supposed to... Well. I think I will take Lilybiris advice and move from cptl files to cptx files etc. entirely. It does not fix the current issue I'm having, but luckily the issue does not ruin my content or anything like that at the moment.

[RodWard]

Thank you.

By the way, I think what Lilybiri means by "locking the file in the OS" is just to set the Properties of the CPTX file to READ ONLY.  That way it cannot be changed inadvertently when someone uses it as a starter project.  As soon as they try to save changes they will be prompted to Save As and give the projec a different name.  That allows you to use the CPTX file as if it were a template.

I fully agree with you that there is no point having a 'template' file format that cannot in practice be used as a template.  I think the concept was intended to work similarly to a PowerPoint POT file, which is also a type of template.  But since Adobe doesn't always fix known issues in Captivate unless a large number of users are screaming about it, this one has just persisted for several versions without being addressed. 

It does not reflect well on Captivate, which I believe to be a very good app overall.