Print/Export triggers/variables

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. 

You can always share ideas for feature requests here. 

Yes please. The ability to print out all the triggers, and variables for projects would be a great asset to learn and plan from. I have added a feature request

Thanks Jane for sending in the feature as well! It's always appreciated. 

I too would really love to be able to print the variables and I have just submitted a feature request.

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.

Hi Jay,

As I mentioned a couple of months ago, there are a lot of requests and I gathered them to share with the team in a unified report.

This feature hasn't bubbled up to the top of our roadmap, but yes, it's been looked at.

How do we push this forward? Maybe we get a grassroots effort to flood the feature request email with this?

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.

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.

Thanks!