Print/Export triggers/variables

Earlier this week I was looking for a way to print out Triggers and today I was looking for a way to print out variables. It doesn't need to be "pretty" - just functional.

It's been 3 years since I last looked at this thread.  I know a number of folks have requested this feature - before and since.

Any change this has actually been looked at?  It's been a long time.

That would be a great feature. How can I submit this as a feature request?

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!

I've submited a feature request but thought I'd also add my comment here. This is a much needed feature in my opinion. When you are working with over 200 slides with approx 7 triggers per slide, there needs to be a better way to view triggers. It would be much more time efficient to look down a list of them all than click on each slide and layer individually. Often theres just one trigger that's causing chaos and it's hard to find if you have to look at everytihng in isolation

Hi Tony,

It's not currently possible to do so, but you wouldn't be the first one to request that as a new feature. 

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.

Ashley

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

TC

Thanks Tony for sending along a feature request, as those go to our product development team for review. And, your suggestion about a way to see what features have been requested is something I know other users have asked for too.

If we can help with anything else just let us know! 

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.