Skip to main content
M
met547
Inspiring
July 18, 2014
Answered

Advanced Actions and Variables from Template

  • July 18, 2014
  • 1 reply
  • 809 views

I created a template in Captivate 8, which includes several user variables and advanced actions (the template was originally created with Captivate 7.)

When I create a new project from the template, Captivate automatically creates doubles of all user variables and advanced actions modifying the names slightly (adding numbers at the end). The thing is now I have twice as many actions and variables, and Captivate doesn't allow me to delete the actions referenced by the template. How can avoid this?

Is there any way to go back to the original set of user variables and actions on my project? Thank you.

This topic has been closed for replies.
Correct answer Lilybiri

Upgrading often causes this kind or problems. Normally you should be able to delete the variables easily in CP8 but of course, I do avoid upgrading especially when features have changed as is the case now with the shared actions in CP8. I agree that it would be easier if upgrading always worked smoothly, but learned after so many years with software that it is rarely the case.

The case you are describing is perfectly fit for shared actions, I even used it as example in a webinar I did (still for CP7) and certainly want to show it again if I ever get the chance to do another one or to offer a training. Creating a library with shared actions that you can use over and over again is now no longer a daydream. No need for a template anymore to reuse advanced actions.

Lilybiri

1 reply

Lilybiri
Lilybiri
Legend
July 18, 2014

Why do you not use shared actions?

I didn't test this in Captivate 8, normally those variables shouldn't be recreated with another name at all. Are the advanced actions duplicated as well with another name?

It does happen for shared actions that have variables, when you use those variables in several actions and drag them from an external library directly to an event in a new project. Since shared actions appeared I don't use templates anymore for reusing advanced actions/variables. I'm prepared to check out your problem if you give some more details about your work flow: what kind of actions, are they triggered by one or multiple events (which events), and how did you use the template. I'm asking this because terminology is often a problem for me: some people use the term 'template' for a file they'll duplicate for reuse, instead of creating a Project from template.

Lilybiri

M
met547Author
Inspiring
July 21, 2014

I should start using shared actions, you are right.

I created originally the template (cptl) in Cp 7, then upgraded to Cp 8, and continued developing my template with Cp8. When I finally created a project using From Project Template, copies of ALL variables and advanced actions appeared in the project file (cptx). Since I couldn't get rid of the newly created variables and actions, I tried something else. I went back to the develop the template with Cp7 using the last version of the template where I used only Cp7. After I finished the template in Cp7, used Cp8 to create a project From Project Template, and now everything worked ok. No doubles or copies of the variable and actions.

I don't know if there are any issues when Cp8 opens template developed with older versions of Captivate, but my opinion is that this should not be happening. I didn't really have any complex actions, I just implemented a simple menu to navigate through the course, so basically showing/hiding the menu items (smart shapes used as buttons), and keeping track of the of the course sections already taken.

Thanks you so much for your reply.

Lilybiri
LilybiriCorrect answer
Legend
July 21, 2014

Upgrading often causes this kind or problems. Normally you should be able to delete the variables easily in CP8 but of course, I do avoid upgrading especially when features have changed as is the case now with the shared actions in CP8. I agree that it would be easier if upgrading always worked smoothly, but learned after so many years with software that it is rarely the case.

The case you are describing is perfectly fit for shared actions, I even used it as example in a webinar I did (still for CP7) and certainly want to show it again if I ever get the chance to do another one or to offer a training. Creating a library with shared actions that you can use over and over again is now no longer a daydream. No need for a template anymore to reuse advanced actions.

Lilybiri

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