Short answer question or Scrolling Text for Survey?


Once in a while a question like in this thread pops up:

“….students will need to answer short answer questions.  They will not be right or wrong, they will be their thoughts.  Is there a way to have all their answers compile into a final screen at the end?”

It seems logical to use short answer quiz slides, in Survey mode, for this use case. However I prefer to use one of the Learning Interactions, ‘Scolling Text’ for reasons I want to explain in this article, by describing both workflows with their specificities. It is up to you to decide which you’ll use. In both workflows variables will be important, hope you are familiar with them.

Short Answer quiz slides, Survey mode

Setup quiz slides

No right/wrong answer means that scoring has no sense, change the stqtus of the quiz slide to ‘Survey’. Nevertheless a score slide will be inserted but you can hide it easily.

Answers to quiz slides are stored in a reusable variable, cpQuizInfoAnswerChoice. After a short answer question the variable will contain the text typed in by the learner in the short answer field. Reusable means that the value will change after each short answer slide. Since we need to store each answer safely (for reusing on the slide at the end), you will need:

  • to create a user variable for each short answer question; I will label them v_First, v_Second, v_Third for the example you’ll see in the demo movie;
  • the default answer area is pretty small (one line), if you expect longer answers, make sure to increase the height of the answer area. It is not possible to edit the used master slide because it applies to multiple types of quiz slides;
  • the content of the system variable cpQuizInfoAnswerChoice is updated when the Submit button is clicked; it has to be transferred to the appropriate user variable, using the After Survey event; for that purpose I created a shared action with two commands:
    Assign v_First with cpQuizInfoAnswerChoice
    Go to Next Slide
    only parameter is the user variable (here v_First)
  • apply this shared action to each of the question slides, with the appropriate parameter.

Setup Answer Review slide

In the example movie I created one text container (shape or caption) and inserted the three user variables in it. Be careful to increase the number of characters to be shown when inserting the variables. You’ll also have to leave enough space for each variable. Of course you could create multiple text containers and/or have the answers distributed over multiple slides.

Using Scrolling Text interactions

A limitation of Short Answer quiz slide is that you can have only one answer per slide. When using a Scrolling Text interaction you can have several question on a slide as you can see in the example movie.

Setup interaction

Setup of the first answer box can be seen in this screenshot:

Two important items are indicated  in the screenshot:

  1. You have to type in the name of the variable to be used. There is no way to use a dropdown list. Beware: you have to create the variable, it is not created uatomatically.
  2. To allow text to be typed in by the user, the checkbox ‘ReadOnly’ has to be unchecked. By default it is checked.

It would have been possible to enter the question in the interaction, instead of having it in a separate text container. I preferred not to do it. Reason: if the user adds the answer, instead of overwriting the question, the variable will contain html tags, like <br>.

The Submit button, which you’ll see on the slide, triggers  the (default) action ‘Go to Next Slide’.

Since I reused the three user variables in this part of the example, I have created an advanced action triggered on Enter to empty the user variables with the technique described in this article.:

Setup Answer Review slide

Very easy: duplicate the slide with the interactions, and take out the On Enter action to reset the variables. The interactions are now populated with the given answers. Moreover the learner can still edit those answers, because of the option ‘ReadOnly’ being unchecked. If you don’t want it, check the option ‘ReadOnly’ on this duplicate slide.

It is also possible to use a similar slide for the first workflow with short answer quiz slides. That will be useful if you want indeed to allow editing the answers.

Example movie


The post Short answer question or Scrolling Text for Survey? appeared first on eLearning.

Unusual Use of Shared Actions


It is not a secret that I am a big fan of Shared Actions. It is very rare that a project I’m working on is not using at least one shared action. From what I hear and read, lot of you don’t realize how much time you can save with them. This short article will offer some ideas where Shared Actions are used for (maybe) a totally different situation than you expect.

1. Creation of Variables

If you are reading this post, it is very likely that you use system variables as well as user variables. Do you create user variables in each project, and include a proper description and eventually default values?  I have a list of variables which I use very often in projects, here are some examples:

  • v_null: an empty variable used to check if Text Entry Boxes remained empty after a learner clicked its Submit button, or to reset the variable associated with a TEB.
  • v_counter: as the name tells to track a number of clicks, attempts….
  • v_visit: for situations where the content of a slide has to be different on a later visit, you want to track if the slide has been visited
  • v_one, v_two, v_three….: number of variables that can be used for different use cases, like tracking clicks on hotspots, finishing chapters…

Knowledge fact: when you import a shared action in another project, variables not defined as parameters, will be created including the description and default value.

I have a shared action with a list of Assign commands, one for each of those often used variables. It doesn’t matter what you assign at all. I drag that shared action from my external Library with shared actions to each new project. Variables are ready for use, even as parameters in other shared actions.

2. Shared Action without Parameters

Sounds very strange, because the reusability of a shared action is based on parameters? I already gave a first example of such a parameter-less SA under 1.  It is much safer and easier to transfer a shared action to another project than an advanced action. You use the shared action directly or convert it to an advanced action if you prefer (maybe for more editing). Here is an example:

I use this action to calculate the reference time in seconds (to be used later in calculations) of a frame, mostly the first or last frame of a slide. Defined as a shared action, it needs no parameters. Once dropped into the project Library, I can use it for any frames where I want a reference time.

3. Shared Action as Template

You can copy an object or a slide, which has advanced actions attached to a new project. But that is not always working great. If you have navigation in the advanced action ‘Jump to Slide’, that command will often be reset to ‘Continue’ if that slide is not found. Same for objects, variables etc.

Less known is that any shared action can be used as a template to create an advanced action. In the top left of the Advanced Actions dialog box, you are used to see ‘Blank’ which is the default template for an action. Open the dropdown list, and you’ll find all shared actions in the project as extra templates:

Choose one of them, you’ll have to fill in the parameters, add a name, edit the commands (delete, add as you want) and save as an advanced action.


Do you use shared actions? Did you like these tips? Do you want to have some training about advanced/shared actions? Personalised training is the best way to get to grip with them.

I love seeing comments on my posts, and promised: you will always get an answer!

The post Unusual Use of Shared Actions appeared first on eLearning.

Advanced Actions, Shared Actions, or JavaScript – Which one is right for you?

When you build your eLearning project with Adobe Captivate you have several options for customizing the way the elements or components of your project work. You can control almost every aspect of your project with Advanced Actions, Shared Actions, or JavaScript but how do you know which approach is right for your project?

When I first started working with Adobe Captivate I used Advanced Actions almost exclusively. Part of this was because they worked and part of it was because I was intimidated by Shared Actions and JavaScript. Two things I took away from building a few eLearning projects using only Advanced Actions are 1) it’s a perfectly acceptable approach, 2) it will likely result in the size of your project increasing. I found that the biggest advantage to using Advanced Actions, at least for me, is the ease of troubleshooting and making changes. It’s easy to tweak an Advanced Action when you want to change how something works and, if something isn’t working properly, it’s easy to pinpoint the mistake in an Advanced Action because you can “see” all of the commands in the action and what they are assigned to. The biggest drawback that I have witnessed to Advanced Actions is that the need to build many Advanced Actions can quickly lead to unnecessary bloat in your project. I often found myself writing the same action over and over because I needed to apply it to different buttons or different slides and before I knew what was happening I had 15 Advanced Actions that all did the same thing.

When I overcame my intimidation with Shared Actions I was able to turn those 15 Advanced Actions that did the same thing into 1 Shared Action and apply it in all 15 places that I had used the Advanced Actions and tis, I believe, is the greatest strength of a Shared Action. If you plan ahead, you can build a handful of Shared Action that you can use over and over; getting the same results you would with Advanced Actions without the project size and without the wasted time building additional actions. Another big advantage of Shared Actions is the ability to “share” actions between projects. If you have an action that is common across many of your projects you can export the action from the original project, save it on your computer, and then import it into another project when you need it. Shared Actions may be a step up from Advanced Actions but they aren’t without their drawbacks. You can’t directly edit a Shared Action once it’s been created, instead you will need to use the Shared Action as a template or model for building a new Shared Action. Another potential drawback is troubleshooting, because you can’t “see” what’s inside a Shared Action you are dependent on the names you, or the person who built the Shared Action, provided for the Shared Action’s parameters. This drawback can be mostly avoided with good authoring practices.

A word (or two) about JavaScript. There are very few things I have done using JavaScript that could not be accomplished with either Advanced Actions or Shared Actions. What I have found is that I can often increase my build speed (sometimes dramatically) by using JavaScript and, honestly, there are things I need to do in some of my more advanced projects that I can’t do with either Advanced or Shared Actions.

So, what do I use when I build a project? I usually use mostly Shared Actions with a few Advanced Actions and some JavaScript thrown in. It isn’t unusual for me to build a short Shared Action with some JavaScript attached to it. For example, I might have an Shared Action that allows the author to set the value of a variable and then execute some JavaScript I have attached that performs different functions based on the value of the variable. Could I have done this without the JavaScript? Yes, but if the Shared Action gets over complex and requires the author to input a bunch of parameters each time the Shared Action is used the using JavaScript for that part of the process can be a big time saver in the authoring process.

One final thing, I expect some of you may be thinking, “I don’t know JavaScript, should I learn it?” Should you learn it, it certainly wouldn’t hurt but it isn’t necessary either. Learn Captivate first. Learn what you can do with Advanced Actions and Shared Actions and  then worry about whether or not you should learn JavaScript.

The post Advanced Actions, Shared Actions, or JavaScript – Which one is right for you? appeared first on eLearning.

Using Simple Shared Actions to Simplify Your Captivate Projects

Adobe Captivate projects can quickly grow complex with duplicate actions being applied across the project. Instead of building multiple Advanced Actions to perform the same functions on different slides, buttons, and objects you can use Shared Actions to reduce simplify your project and save time building the project. In this video, I demonstrate a simple Shared Action to take the place of the Advanced Actions controlling the toggles in my sample project.

The post Using Simple Shared Actions to Simplify Your Captivate Projects appeared first on eLearning.

Micro-Navigation with Shared Action (Step-By-Step)


After the introduction to Micro-Navigation I explained how to use it for forcing the first view of a slide, and for playing an audio file on first visit. When looking at the resulting advanced actions they are pretty similar in both posts. Moreover you probably will want to use the action on multiple slides in the course, and maybe also in future courses. That sounds like a perfect scenario for conversion of the action to a Shared action. I have been blogging already several times about Shared actions. In the present article I try to explain how to reflect on the use of parameters. Static objects need to be parameters as are states and groups, I label them as ‘compulsory’. But Variables and Literals are ‘candidate parameters’, a well-founded choice for change them in parameters,  can save you lot of time later on. Consider it a good practice example.


When comparing the two advanced actions created in the mentioned articles, there is a small difference: the first decision (which is a standard action) has one command extra in the second advanced action (for Audio). For the ForceAct, the number of seconds to be jumped over is directly entered in the Expression command, for the SkipSlideAudio, Assign is used to store the number of seconds in the user variable v_skip. Both versions work well, but personally for a shared action I prefer the one with the extra Assign command.

What are the parameters for the shared action?

For the first decision (labeled Always in both advanced actions):

  •  ‘Assign v_skip with 16.5‘: this first command has two candidate parameters, the variable v_skip and the literal 16.5. The variable can be reused on each slide where the action is needed. Both advanced actions used the same variable in the interactive movie. There is no need to promote that variable to a parameter in that case. However the literal ‘16.5’  is the number of seconds to be jumped, will have a unique value on each slide, it has to be promoted to a parameter. Parameter 1 = literal. You have to be careful with literals: double-check that the same numerical value is not used anywhere else in the action. In this example there is a second literal ‘1’ in the second decision, Increment command. It has to be different from the first parameter, which is the case.
  • Expression v_skip = v_skip * cpInfoFPS‘: the user variable v_skip is no parameter (see above). The system variable cpInfoFPS has never to be replaced by another variable, will be no parameter neither.
  • Increment v_visit by 1‘: the user variable v_visit has to be unique for each slide, as you can see in the action SkipSlideAufio where another variable has been used. This means that we have to promote that variable to a parameter, parameter 2. The literal ‘1’ however will always be the same, no need to turn it into a parameter. We already double-checked that the literal in the first decision was different from 1.

The second decision is conditional:

  • IF v_visit is greater than 1‘: has two candidate parameters as well. We already indicated that v_visit is a parameter. The literal in this case will always be 1, will never be changed and need not to be a parameter.
  • Expression cpCmndGotoFrameAnd Resume = cpInfoCurrentFrame + v_skip‘: has 3 candidate parameters. Above was already decided that v_skip can be reused on each slide, and the system variables will always be the same.

Shared action Skip_Frames

When you choose to save any of the advanced actions used to skip frames as a Shared Action you’ll see that all possible parameters are marked as OK. The reason is that there is no compulsory parameter in this action:

As a result of the analysis above, we need to mark to items as parameters: the tracking variable and the number of seconds to be jumped on later visits. The result will look like this. It is important to give a good description not only for the shared action but also for the marked parameters:

You can assign the shared action to all the slides where you want to jump frames on a later visit. You only have to define a tracking variable and estimate the number of seconds to be jumped. Here is one example setup for the slide where audio had to be jumped on later visits:

You can check in the Library for the Usage of the Shared action, much easier than for advanced actions.

Using Skip_Frames in future projects

Want to reuse this action in other projects? The workflow is described in an older blog post. Short summary:

  1. Use File, Import, External Library and point to the project where you created the shared action.
  2. Library will be opened in a floating panel. Look for ‘Skip_Frames’ in the Shared Actions subfolder and drag it to the Library of the new project.
  3. Because v_skip is not a parameter in the shared action, it will be created automatically, including the description.
  4. You have to create a tracking variable for each slide to which you want to assign the shared action, and define the duration in seconds to be skipped. Ready!

The post Micro-Navigation with Shared Action (Step-By-Step) appeared first on eLearning.

Intro to Shared Actions

Interactive presentation (webinar)

Last week I presented a webinar ‘Dare to Share: Power of Shared Actions’ for a pretty big crowd.  As usual I presented using a Captivate presentation, since I don’t feel it to be appropriate to use Powerpoint when Captivate has so much more features. One of the advantages is that I am able to convert that presentation in an interactive movie. If you did miss the webinar and did not register to have access to the recorded versions, you can watch this movie using this link:

Shared Actions

It is Rescalable HTML5 output, you can also watch it on mobile devices, but only in landscape mode.

Content of Presentation

Five topics in this presentation:

  1. Importing and using a Shared action
  2. Creating a Shared action (two workflows)
  3. Parameter types
  4. Using a Shared action as a Template
  5. How to choose between Shared and Advanced action

The presentation itself is using a lot of shared actions as you’ll be able to see because I included these screenshots under the ‘Information’ button:

  • To create a dashboard
  • To deactivate an interactive object after all has been viewed
  • To create toggle buttons
  • To skip audio when a slide is revisited
  • In a Drag&Drop slide to show Feedback for each drag action.
  • ….

A lot more is possible with Shared actions to replace Advanced actions and make it easier to transfer the scripts to new projects for reusing. A typical example are custom question slides of all types (not only MCQ). To attribute all fhe functionality of the default question slides to those custom question slides, it takes a lot of work creating the actions. By reflecting on the setup you can create shared actions that can be easily reused not only in the present project but in all your future projects.


Some of the mentioned examples will be published in a later blog post. If you want to learn more about Shared actions, which are a lot more flexible that the older advanced actions, send me a note. I am preparing several booklets. One will be  about  Shared Actions. Those booklets can be used as cookbooks, with recipes but also offer in-depth information about the topci.

The post Intro to Shared Actions appeared first on eLearning.

[Webinar] Dare to Share: Power of Shared Actions

If you have seen some of my use cases or tutorials, you are aware of the fact that I am a big fan of Shared and Advanced actions. Advanced actions are part of Captivate since version 4 and made it possible to extend Captivate’s functionality in many ways.  Their release was the reason I started blogging to show how easy it is to  create engaging courses without the need of learning a programming language. You just use the point-and-click interface of those actions, which are converted to a programming language on runtime.

With Captivate 7 Shared actions were included, a more flexible alternative for Advanced actions. The main goal of those shared actions is reusability!  That reusability is due to the presence of parameters, which can be filled in on assigning a new instance of the shared action to an event. Shared actions will be listed up in the Library, the same way as other assets. As I explained in the blog post Library? Which Library you can open the library of any project in a new project, and drag the assets in the library of that new project. That is also the case for shared actions. Captivate 8 extended the functionality of shared actions by adding the possibility to define variables and literals as parameters.

Shared actions can also be used as templates for new advanced (or shared) actions, a feature that is not very well known but very useful as well.

If you want to see shared actions ‘in action’, you can register for this webinar, organized by the eLearning Brothers on Thursday, 15th of March,  4pm CET (8am PT). You are welcome to get lot of tips from a user addicted to shared actions. Registering is possible using this link:

Dare to Share

Be sure: you’ll walk away with many creative ideas!  As a plus: you’ll be working in the brand new Advanced Actions dialog box of Captivate 2017.

Shared Actions in Drag&Drop


Shared actions were a new feature in Captivate 7 and were improved in Captivate 8. Nevertheless I rarely see examples of shared actions, and there is also lot of misunderstanding.  Some users think they can only be reused in other projects. I did see experts claiming that they are totally useless, that it is much easier to duplicate advanced actions. I don’t agree with that opinion, about 90% of all the project I have developed do include shared actions. They are especially useful for responsive projects as well. In a recent article you can find links to tutorials about shared actions.

A problem that still remains is that you cannot edit an existing shared action, had hoped that would have been solved in 9 in a recent version but it didn’t happen. The reason is probably that since they are not much used, this improvement doesn’t get on the priority list. If you want to learn more about how to create shared actions and see some examples, have a look at this recent article in which I summarized several older posts. This post is a showcase, where I’ll try to explain when to use a shared action, and when you cannot use them. The origin of this showcase is due to this question in the forums. The answer I gave there is working, but has a serious drawback, I will explain both this first simple answer, followed by a second version that will work in all situations. I hope you learn from that workflow: test out all possible situations, even though they seem to be improbable. As a trainer/coach never underestimate how trainees will explore courses.


User did look for a solution to apply to this use case:

  • Drag&Drop slide with two drag sources and two drop targets
  • Each drag target should accept only one drag source
  • Depending on the sequence of the dragged items, one out of two texts should appear.
  • Learner can switch the drag sources
  • Auto submit for the answer.
  • Slide needs a reset button

Example movie

It is not possible to embed an iFrame here, you will have to use this  link to see the two proposed solutions.

You can test the problem with the first solution as well. Everything works fine if you switch only once, like first dragging the First text to the Top target, than drag the Second text to the Top target. However if you switch a third time, First text to the Top target, you’ll see that the functionality is lost. This will not happen with the second solution

Setup Drag&Drop slide

The setup is the same for both solutions. Drag sources are shapes and labeled SS_DragOne and SS_DragTwo. The shapes acting as drop targets are labeled SS_DropTop and SS_DropBottom. The feedback will appear in another shape SS_Feedback, which has 3 states: Normal, OneTop (first scenario with SS_DragOne in SS_DropTop) and TwoTop (second scenario (SS_DragTwo in SS_DropTop).

Since Auto Submit is turned on in the Actions tab of the Drag&Drop panel, I dragged the Submit button out of the way to the scratch area.

That means that both possible answers have to be defined as Correct answers. This can be done with the button ‘Correct Answers’ on the Options tab of the Drag&Drop panel.

Each drop target should accept only one drag source, but the learner can switch them if wanted, as long as no correct answer has been defined. For that reason editing the dialog box ‘Accepted Resources’ is necessary, because the default setup is that each Drop target accepts all drag sources. This dialog box can be opened from the Format tab of the Drag&Drop panel, when a drop target is selected. It has to be repeated for both targets. Rest of the setup like snapping behavior is not important for the rest of the workflow, do what you like.

First solution

This solution is using two variables: v_first and v_second. They are related to the first scenario (SS_DragOne in SS_DropTop and SS_DragTwo in SS_DropBottom) and the second reverse scenario. Default value of the variables is 0.

I used the same shared action for all object actions, for both targets. It is pretty simple, conditional with one decision. It has three parameters:

  1. First parameter is the variable associated with the scenario, v_first or v_second.
  2. The multistate feedback object is the second parameter
  3. The state to be shown, which fits the scenario is the third parameter.

This was the original idea:

  • When the first drag action occurs, it fits into either scenario 1 or scenario 2; the appropriate variable is set to 1.
  • If the drag source is replaced on that same target nothing happens.
  • When the second drop target is filled with the other drag source, it has to be in the same scenario. Checking if that associated variable has a value=1, means that both targets are filled, and the feedback is shown, depending on the scenario variable.

What is the problem with this action? It works fine until the user changes the object twice on the first target: in that case the feedback will be shown to early. That was the reason for the second solution which does avoid this problem.

Second solution

Besides the two scenario variables, a third variable to track the number of drag actions was created: v_counter. It started also with a default value of 0. The shared action now has 3 decisions as you can see in this Preview:

The first decision ‘Always‘ is a mimicked standard action. The increment command for both v_counter and the associated scenario variable (v_first or v_second, depending on the object action) will always be done.

The second decision ‘Complete‘ checks if both targets are filled, which is the case when both v_counter and the associated scenario variable have the value = 2. In that case the correct feedback is shown (similar to first solution).

The third decision ‘Incomplete‘ is the one that solves the problem with solution 2. If there has been 2 drag actions (v_counter is equal to 2) but the associated variable for the active object action is still set to 1, that means that the user has switched the drag sources on one target two times. In that case the variable for the other scenario (which probably has already a variable different from 0) is reset to 0.

It is not necessary to define v_counter as parameter, since it will be used as counter whatever the scenario. This action needs 4 parameters, because both v_first and v_second are used in the action; whereas in solution 1 only one of them was used..


This is not the default Reset from Drag&Drop, because it will not reset the variables nor the state of the feedback container. I used the usual workaround (micronavigation as explained in ‘Replay Slide‘ is not possible yet due to a HTML5 bug in CPwhere the On Enter action is not executed) to reset the variables and that feedback container. Two dummy slides with a duration of 0,1sec are inserted: one before each D&D slide. The reset button triggers the command ‘Go to Previous Slide’, thus forcing the playhead to re-enter the D&D slide.

The On Enter action ‘EnterDD‘ is also a shared action and looks like this:

I used that action for both D&D slides, even though v_counter is not used in the the first solution.

I hear you! Why a shared action, you only need it twice, and the only edit to make to a duplicate advanced action is the label of the feedback container. If you were one of my college students, you would know that ‘Weymeis never acts without a reason….’. I will try to explain why I preferred a shared action with two parameters, instead of two advanced actions.

When you import this shared action in a new project by dragging it to the Library from this project opened as External Library (see Libraries) the variables v_counter, v_first and v_second are created automatically in that new project, with their definition and default value. That is a time saver, something to take into consideration when creating shared actions. This happens only for variables that are not defined as parameters.


Do you want to try out those actions? Send me a mail ( and tell me if you use shared actions, or will use them in the future?  As a 2018 offerI will send you a project that you can use as external library with the two shared actions (EnterDD and DragSequence) described in this blog post, and instructions how to use them.

Managing Advanced Actions

When managing Advanced Actions in Adobe Captivate, I recommend that you open the Advanced Actions window from the drop down menu rather than from the Actions tab in the Properties of a slide or object. This way you reduce the risk of accidentally selecting a new Advanced Action in place of what was there from the start. Click on the Project dropdown menu and select Advanced Actions. Alternatively, you can press SHIFT+F9 (which doesn’t always work for me) to open the Advanced Actions window. Once open you can scroll through all the Advanced Actions in your project using the Existing Actions selection drop-down shown below.

2018-01-27 1-26-32 PM

You should become familiar with the toolbar controls just above this drop-down selection box.

toolbar1The first icon is Preview Action. This makes Advanced Actions easier to read and share with others. Normally items like your Else statements are collapsed so using Preview Action will show the entire script in one list. If you want help troubleshooting Advanced Actions on the forum, using the script as it’s written here is helpful to the other users assisting you. Here is an example Conditional Action I have for one of my projects:

2018-01-27 1-20-57 PM

toolbar2The next icon is the plus symbol and allows you to start making a new blank Advanced Action.

toolbar3After that is the import icon which allows you to import Shared Actions. A well created Shared Action is completely reusable and can be shared across more than one project. It also can be used multiple times within the same project just by changing the parameters that reference various objects and variables used throughout your project. Here is a video tutorial I did some time ago on Shared Actions if you would like to learn more:

toolbar4The next icon is to export Shared Actions and will be greyed out if you don’t presently have any Shared Actions in your project. Captivate Shared Actions can be saved as a CPAA file format but they can reside as part of your Captivate Library if you don’t need them to be stored outside of a single project file.

toolbar5This is the delete action icon and its function is self explanatory. I use this when I’m feeling overwhelmed by all the extraneous Advanced Actions I might end up with in an eLearning project. This is mostly due to starting an Advanced Actions and then abandoning it and rewriting it and so on. The good news is that if you try to delete an Advanced Action that is in use somewhere in your project you will get a warning like the following:

2018-01-27 1-46-05 PM

Just be careful when deleting these advanced actions that you don’t delete something you actually need.

toolbar6Lastly is my favourite icon from this section and that’s the Duplicate Advanced Action icon. As the name suggests this icon will make a copy of the currently selected Advanced Action. You will find that there are many sets of advanced actions that are reused. The modern solution for cases where you need a similar version of an advanced action duplicated is to simply use Shared Actions. Duplicating actions and making a few small changes to them was the way things were done before Shared Actions were introduced in Adobe Captivate version 7. Also some people are just more comfortable making a new action from the old action. The duplicate action will be named “Duplicate_Of_” followed by the original name and then a number to make sure that duplicated actions are named something already in use.