Skip to main content

🎓 Lesson 18: Variables & Advanced/Conditional Actions — Classic's Power

This is where Captivate Classic Classic flexes muscle the all-new tool is still growing into: variables that remember things, and advanced/conditional actions that make decisions. It can sound like programming — but it's really just logic you can read out loud. This tour gives you the concepts and one worked example, so you recognize the machinery behind personalized, branching, and gamified courses.

📚 What You'll Learn

By the end of this lesson, you will be able to:

  • Explain what a variable is and tell system variables from user variables
  • Describe an advanced action as a saved sequence of steps
  • Read a conditional action as plain IF/THEN/ELSE logic
  • Walk through a simple worked example (a name greeting, and a pass/fail branch)
  • Recognize why this engine powers personalized, branching, and gamified courses — and check what the all-new tool now offers All-New

⏱️ Estimated Time: 35 minutes

🎯 Project: Plan one user variable and one conditional action in plain English (on paper is fine), then read the logic aloud to check it makes sense.

In This Lesson

It's Logic, Not Code

Let's disarm the scary word first. When people say a Captivate course is "smart" — it greets you by name, remembers your answers, branches to different content based on your score, tracks points like a game — that intelligence usually comes from variables and actions. And in Classic you build all of it without typing a single line of code. You pick from menus and fill in blanks.

🧠 The reframe that makes this easy

You already use this logic every day. "If it's raining, then take an umbrella, else wear sunglasses." "Remember where I parked." "Add one to my coffee count." Variables are just remembering, and conditional actions are just if/then/else. Captivate gives you a friendly form to express exactly that. If you can plan it in a sentence, you can build it.

Because this is a survey, we're after understanding, not fluency. You won't leave able to build a complex branching game — but you will be able to read someone else's advanced action, understand what a variable is doing, and know what's possible so you can decide whether a project needs this power (and this tool).

Variables: the Course's Memory

A variable is a named container that holds a value which can change — a labeled sticky note the course can read and rewrite as the learner moves through it. It might hold a name, a score, a count, or a yes/no choice. Two kinds matter:

  • System variables — built in and maintained by Captivate. They already know things like the current slide number, the quiz score, or the total slides. You mostly read these.
  • User variables — ones you create for your own purposes: a learner's name, a running points total, whether they chose "beginner" or "advanced." You create, name, and update these.

Two everyday things you do with variables:

  • Display a variable's value in text, so a caption can literally say the learner's name or current score. In Classic this is done by inserting the variable into a text object.
  • Update a variable with an action — set it, add to it, or copy another value into it — as the learner does things.

🔤 A tiny concrete picture

Imagine a user variable named learnerName, empty at the start. Early on, the learner types their name into a text-entry field, and an action copies it into learnerName. From then on, any caption that displays learnerName greets them personally: "Nice work, Priya!" One variable, remembered once, reused everywhere. That's the whole idea.

💡 Naming matters more than you'd think. Give variables clear names — quizScore, not x1. Months later (or when a teammate inherits your .cptx), readable names are the difference between logic you can follow and a puzzle you have to reverse-engineer.

Advanced & Conditional Actions

An action is simply "do something" — show an object, jump to a slide, play audio, assign a variable. A simple action does one thing. Classic then gives you two more powerful kinds:

  • Advanced actions — a saved sequence of steps that run in order, like a recipe: "hide the hint, add 10 to the score, show the 'well done' caption, enable the Next button." One trigger, several coordinated results.
  • Conditional actions — an advanced action with a decision in it: IF a condition is true, THEN do one set of steps, ELSE do another. This is the branch that makes a course react to the learner.

Here is a conditional action drawn as the plain IF/THEN/ELSE it really is. Notice we describe the score comparison in words — "score is at least the pass mark" — rather than with symbols:

graph TD A["🏁 Learner finishes the quiz
(trigger fires the action)"] --> B{"IF quizScore is
at least the pass mark?"} B -->|"Yes — score ≥ pass"| C["THEN branch:
show 'You passed!'
go to the certificate slide"] B -->|"No — score is below pass"| D["ELSE branch:
show 'Not yet — try again'
go to the review slide"] C --> E["✅ Course continues
on the right path"] D --> E style A fill:#bfdbfe,color:#1e293b style B fill:#fde68a,color:#1e293b style C fill:#bbf7d0,color:#1e293b style D fill:#fecaca,color:#1e293b style E fill:#c7d2fe,color:#1e293b

Figure 1 — A conditional action reads as IF / THEN / ELSE: check whether the score is at least the pass mark, then send the learner down the matching branch.

That single pattern — check a variable, branch on the result — is the seed of an enormous range of behavior: personalized feedback, adaptive paths ("you struggled here, here's extra practice"), gated navigation ("finish this before Next unlocks"), and points-based gamification. Stack a few conditions and you have a course that genuinely responds to each learner.

⚠️ Power invites over-engineering

Just because you can build a ten-branch adventure doesn't mean a compliance module needs one. Start with the simplest logic that serves the learning goal. A single well-placed pass/fail branch often does more good than a maze of conditions nobody can maintain — including future you.

A Worked Example You Can Read Aloud

Let's assemble the pieces into something you could actually plan, told entirely in plain language. Picture a short course with a friendly greeting and a final check.

Figure 2 — Captivate Classic (a simplified mock-up, not a real screenshot): a caption displays the learnerName variable; a text-entry field captures it. The $$name$$ style shows where a variable's value drops into text.

Read the plan aloud, step by step:

  1. Create a user variable called learnerName, starting empty.
  2. Add a text-entry field; when the learner types their name and continues, an action stores it in learnerName.
  3. Put learnerName inside a greeting caption, so it reads "Welcome, Priya."
  4. At the end, a conditional action checks the built-in score: IF quizScore is at least the pass mark, THEN show "You passed!" and go to the certificate; ELSE show "Not yet" and go to the review slide.

✅ Notice what just happened

No code. Every line above is something you'd assemble by choosing from menus and filling in blanks. If you can say the logic clearly, Classic's action editor is mostly a matter of translating your sentences into its dropdowns. Plan in plain English first — always.

💡 The all-new tool is catching up. All-New Adobe Captivate has been steadily gaining variables and logic/interaction features release by release. Deep, fully-featured conditional advanced actions have long been a Classic strength — but before you choose Classic just for logic, check what your current all-new version can already do. This is a moving target, by design.

🎯 Try It: Plan a Variable & a Condition

🏋️ Activity: Write the logic in plain English (about 15 minutes)

Objective: Practice thinking in variables and conditions. Planning on paper is the real skill here; building it in Classic is a bonus if it's installed.

Steps

  1. Invent one user variable for a course you care about — a name, a points total, a chosen difficulty. Give it a clear name and a starting value. (⏱️ 3 min)
  2. Write one sentence describing when and how it changes ("when the learner clicks the correct answer, add 10 to points"). (⏱️ 3 min)
  3. Write one conditional action in IF/THEN/ELSE form using words, not symbols: "IF points is at least 30, THEN unlock the bonus slide; ELSE show an encouraging hint." (⏱️ 4 min)
  4. Read it aloud. If it makes sense spoken, it'll make sense in Captivate. Fix any step that sounds fuzzy. (⏱️ 2 min)
  5. In Classic (optional): create the user variable, then open the advanced-actions editor and translate your sentences into a conditional action. (⏱️ 3 min)
💡 Hint

Stuck on the condition? Every conditional needs three pieces: what you're checking (a variable), what counts as true (at least the pass mark, equals "advanced," is not empty), and two branches (THEN and ELSE). Fill those three blanks and you have a valid condition. Keep the comparison in words to sidestep any symbol confusion.

✅ Activity Complete When…

  • You've named one user variable, its starting value, and when it changes
  • You've written a conditional action as clear IF/THEN/ELSE in plain language
  • You can read the whole thing aloud and it makes sense

🎯 Quick Quiz

Question 1: What is a user variable in Captivate Classic?

Question 2: What makes a conditional action different from a plain advanced action?

📓 Learning Journal

Keep your Learning Journal going — a note in your favorite app, a doc, or a paper notebook. It's where you turn "I read that" into "I can do that." After each lesson, jot down:

  • Key concepts you learned
  • Things that clicked for you
  • Questions or confusion points to revisit
  • Ideas you want to try
  • Your progress and how you feel about learning this

✍️ This lesson's prompt: Did "variables and conditional actions" feel like coding before this lesson, and does it now? Write one variable and one IF/THEN/ELSE you'd genuinely use in a course you care about — in plain English. Notice how much of "programming logic" is just careful sentences.

📝 Lesson Summary

🎓 Key Takeaways

  • A variable is the course's memory: system variables are built in (score, slide number); user variables are ones you create (name, points, choice).
  • An advanced action is a saved sequence of steps; a conditional action adds an IF/THEN/ELSE decision that makes the course react.
  • This engine powers personalized greetings, branching paths, gated navigation, and gamification — all built by menus, not code.
  • Plan the logic in plain English first; deep conditional logic is a Classic strength today, but check what the all-new tool now offers before choosing Classic for it alone.

🎉 What You've Accomplished

You just demystified the feature that scares most beginners away from Classic. You can define a variable, read a conditional action as IF/THEN/ELSE, and plan a personalized, branching interaction in plain language. That's the concept locked in — and it's the concept, not the clicks, that transfers everywhere.

❓ Common Questions at This Stage

Do I need to know how to code to use this?

No. Everything here is built by choosing from menus and filling in blanks. The only "skill" is thinking clearly in remember this (variables) and if/then/else (conditions) — which you already do in everyday life.

Is this only in Classic?

Deep, fully-featured conditional advanced actions have been a Classic hallmark. The all-new tool keeps gaining variables and logic features, so the gap narrows over time. Before picking Classic purely for logic, check what your current all-new version can already do.

How much logic is too much?

When it stops serving the learner or nobody can maintain it. Reach for the simplest branch that meets the goal. One clean pass/fail condition usually beats an elaborate maze — clarity is a feature.

🔭 Looking Ahead

In Lesson 19 — the last of Part 4 — we tour Classic's mature software simulation, its VR/360 projects, and interactive objects, then wrap up your Classic survey.

✅ Before the Next Lesson

  • Do the plain-English variable + condition exercise if you haven't
  • Write this lesson's journal prompt — did logic feel like coding, and does it now?
  • Remember the mantra: plan the sentence, then build the dropdowns

📚 Additional Resources

🌟 Encouragement for the Journey

You just looked "programming logic" in the eye and found sentences you already know how to say. That confidence — I can plan this, I can read this — is exactly what separates authors who reach for interactivity from those who avoid it. You're firmly in the first group now.