18 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.

Moodle.org 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

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.