Collaboration and Captivate

[ChristineID45]

A co-worker and I are creating different parts to the same captivate project.  When we are ready to combine what is the best way to make sure that all the advanced actions follow?  Our first attempt was not successful.  Everything except the advanced actions came over.  Any suggestions?  Thank you.

[Lilybiri]

Whenever possible replace the advanced actions by shared actions. They will transfer much better, and if necessary you can change the parameters. Copy/paste to another project will often result in adding a number to the names of items, hence my recommendation to use shared actions.

I suppose you are usting the same custom theme?

Especially advanced ations triggered by slide events will cause problems with copy/paste. Navigation to slides: try to avoid indicating slide numbers, but use slide labels. If possible put custom buttons on master slides, they are part of the theme.

[ChristineID45]

I'm not sure how to create shared actions.  We are creating a prototype course to show our faculty so we are both just using the blank theme. 

[RodWard]

What version of Captivate are you both using?

For some versions now it has been possible to copy and paste slides from one project to another and the Advanced Actions and Variables that are referenced in the copied slide will then be carried over to the new project.  However, you need to remember that if your Advanced Actions in the original project are referencing slides that will not be present in the new project, then any dynamic navigation (e.g. Jump to Slide actions) that you have baked into the Actions will probably revert to a standard Continue action when copied to a new project.

[ChristineID45]

We are both using 2017.  Thank you the information about what to keep in mind when we transfer over.

[Lilybiri]

Contrary to copy/paste for advanced actions, which is not always foolproof, especially if they are linked to slide events (interactive object events are easier to copy/paste), shared actions transfer is very easy.  To be honest, in most projects I use more shared than advanced actions. You can have a look at my blog and at this movie:

SharedActions

Rare Tips for Shared Actions - Captivate blog

Advanced to Shared Action: Step-By-Step (micro-navigation showcase) - Captivate blog

As for what I wrote about themes: I understand you start from the Blank theme, but I suspect that you did use other colors than those in the Blank Theme Color palette, that you did create new object styles, added content master slides, maybe changed the skin. Why not save all those components in a custom theme? It will save you a lot of time as for consistency in design if you are working on the same project with different developers. Have a look at:

What's in a Theme - a Template? - Captivate blog

[ChristineID45]

Thank you for all the videos and blogs.  I will definitely look at them.  As far as the theme goes, the only thing I have changed so far is adding some text and shapes and making them smart buttons.  We want to get approval for the content before we "make it pretty."

[Lilybiri]

Every developer has his own workflow. I always start by creating at least a Theme Colors palette, and some styles. It is more than making it 'pretty',  you asked about collaboration, offered you all my suggestions for an efficient collaboration and using the same theme is certainly one of them. If you start by overriding most styles you'll have a lot more work later on to make it 'pretty'.

[ChristineID45]

Thank you for all of your ideas.  We are learning alot through this process.  I do see how making a theme in the beginning is helpful.  Thank you again.