Forum Discussion
Print/Export triggers/variables
Hi,
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.
TC
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:
- Read the triggers out loud to be sure they make 'sense' and are in the right order.
- Focus on one timeline object at a time, if applicable.
- 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 :)
- BethCase-c92276Community Member
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!
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.
- LouisaAntoineCommunity Member
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,
LouisaSent 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
T:
0207 4639 316
E:
Louisa.Antoine@ssafa.org.uk
W:
www.ssafa.org.uk
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.
- BethCase-c92276Community Member
How do we push this forward? Maybe we get a grassroots effort to flood the feature request email with this?
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.
- JayFrischkornCommunity Member
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.
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.
- LouiseAntoineCommunity Member
I too would really love to be able to print the variables and I have just submitted a feature request.
- DMCommunity Member
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!
- LindaVincent-SmCommunity Member
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.