Print/Export triggers/variables

Sep 16, 2014


Is it possible to export, or print, a list of variables or triggers?

For documentation of a project it would be very handy to be able to export a list of the triggers and variables so we can make it easier to pass projects between developers.


33 Replies
Tony Chilvers

Rebecca Fleisch Cordeiro said:

Hi Tony,

I remembered that someone had posted how to export variable to a PDF. As Ashley indicates, not Articulate-supported.

Haven't tried it myself, but figured I'd point it out.

Thanks Rebecca,

That is really useful, but more of a runtime solution to return the value of given variables.

What I am trying to achieve is a simple method of effectively documenting the variables/triggers so it would be easier for one of our learning designers to pick up another's work.


I have submitted a feature request, 421930, as you suggested.

One suggestion for the feature requests, would be the ability to see other requests and be able to add my voice. have a very good system for tracking change management and feature requests, have a look.

Oh well back to the drawing board...


Jay Frischkorn

Apparently this hasn't come up for over a year.  But it is still essential to be able to quickly and easily document triggers and variables used for each page of the course when trying to debug and/or maintain courses.  It is also an excellent teaching tool for eLearning teams to explore process improvements and consistency - not to mention not needing to reinvent the wheel each time someone sits down to develop.  Too bad this hasn't been added.

Ashley Terwilliger-Pollard

Hi Jay,

I don't have any updates on this type of feature, in regards to if or when it would be included. If you're using Storyline 2, you can undock the triggers panel to make it larger and then you'd be able to look at screen capturing a larger portion of it that you could use to print or share with others. 


I have the same need to be able to print out or document all triggers used in a course - just posted a feature request today.  To reiterate Linda, it doesn't need to be pretty, just functional.  Good for planning  and for really complex projects where being able to see the big picture could help with problem solving!

Leslie McKerchie

Thanks for submitting your feature request as well, Louisa. It's been a while since we've seen any conversation here, but I see that there have been quite a few submissions. 

I've gathered these together for a better reflection of the user request for our team.

I wanted to share some information about how we manage these feature requests as that may be helpful.

Leslie McKerchie

Hi Beth,

Thanks for reaching out. It sounds like this is a feature that you would like to see implemented as well.

I wanted to share some information about how we manage these feature requests as that may be helpful. As I mentioned previously, this is not at the top of our roadmap yet, but we are monitoring the user requests for this.

Would you be able to share how you would use this feature or why this is needed for your situation? That information is really helpful.

Louisa Antoine

Hi Leslie,

The main reason is for finding triggers that have not been set up correctly.

It isn’t possible to view all of the parameters in a trigger without double clicking to open it. You can look at a trigger in the list which looks as if it has been set correctly, but only once opened can you see that there is an issue.

So essentially it is to provide a quick view of all the parameters in a the triggers on a particular layer for trouble-shooting .

Kind regards,

Sent from Mail for Windows 10

Louisa Antoine
E-Learning Business Partner
SSAFA, the Armed Forces charity. Queen Elizabeth House, 4 St Dunstan's Hill, London. EC3R 8AD
0207 4639 316
​The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Registered Charity No. 210760 Est. 1885. Registered charity in England and Wales No. 210760, in Scotland No. SCO38056 and in Republic of Ireland No. 20006082. Est. 1885.

Beth Case

Sorry I posted this in a few threads, but it seems such a common question! I read the post on how requests are handled, but this has been asked for several times going back at least 7 years, so it's clearly something people want. Anything you, or we, can do to bring it more attention would be appreciated! :)

I tend to use very long, complicated series of triggers with variables. You can only see a few on the screen at once. So here are the situations where I would find it REALLY useful to be able to print them out.

1) Something isn't working as expected. Since you can't see them all at once, it's hard to track where the problem might be.

2) If I go back to something I created a while ago, it's sometimes hard to remember how I set it up and need to review the triggers to figure it out.

3) If I'm editing a project that someone else initially created, I need to be able to see how they set up their variables and triggers.

Even though this isn't technically coding, it kind of is. Anyone who has ever coded knows that sometimes you just need to spread it all out on the table to figure out why something isn't behaving as expected. It's just too hard when you can only see a handful of triggers at once, sometimes only the triggers for one variable.

If this is too difficult to implement for some reason, then a way to be able to expand the trigger section to be able to see many more (at least 20-30) at once might work, though it's still really nice to be able to write and make notes while troubleshooting.

Did I mention I tend to have a lot of triggers?

You all create some very complicated Storylines. How do your people manage troubleshooting when you can't see many triggers at once or print them out? Maybe there's just  technique that would help.



Leslie McKerchie

No worries on the multiple postings, Beth. It helped me identify a couple of additional conversations that were not tied to our report.

I appreciate you sharing how this would be helpful to you and I've shared these thoughts with the team.

How do we manage...that's a great question. I can only speak for myself here, but I tend to:

  1. Read the triggers out loud to be sure they make 'sense' and are in the right order.
  2. Focus on one timeline object at a time, if applicable.
  3. Undock the triggers panel to get a better view if needed as well.

I'd love to hear from others in how they manage many triggers as well :)

Leslie McKerchie

Hello everyone,

I wanted to pop in and let you know that we released an update to Storyline 360 today, which included a trigger panel and workflow update to make it faster and more intuitive.

I know it's not an answer to your specific feature request. Still, many of the details that we've gathered around the need for printing the trigger panel are specific to:

  • viewing and troubleshooting a long list of triggers
  • understanding all the triggers tied to a particular action or event.

With the new triggers panel, you'll be able to:

  • Inline edit - No need to open the trigger wizard
  • Group view - Organize by an event to make it easier to find, edit, and debug.
  • Disable Individual Triggers - No need to delete during your troubleshooting.
  • Collapse and Expand - The ability to focus on specific triggers.

You can read all about this new trigger workflow as well as check out a video right here.