Has anything been done on this (6 years later)? I can SNAGIT but there has to be an easy way to print the whole thing. When I am doing branching scenarios, I'd like to be able to scope out the project with temporary blocks and then print it. Please add this feature back to the list if it has somehow disappeared. (even better if it could also be sent to Review) Thanks
Thanks for chiming in to share your thoughts as well.
It hasn't gotten lost, I can still see that this is open with our team. You are obviously using Storyline 360 since you mentioned the use of Review as well, so I'll be sure that this conversation gets added to that report.
Speaking of Review, curious how sending the StoryView to Review would fill a need or use-case for you? I'd like to hear more about that.
This feature hasn't bubbled up to the top of our roadmap, and that's the point at which we could better identify an ETA, but we're still listening to the feedback! Here's a bit more about how we work to prioritize feature requests.
Just had this request yesterday for a course where you take a quiz question, if correct go to next question; if not get several slides of content. Requestor wanted to show how a competent employee would only see a few slides while others would get topic-specific content. Also wanted to see the draft questions and content at the same time. I got around it by creating each question branch as a separate scene but printing the tree would have been way better.
Is the roadmap made available to A360 subscribers?
...if not, why not? There are many new apps competing with immersive experiences/features it would be great to be able to share with management what is comping up in future feature releases and this would also assist in convincing my team not to go to another product.
Is there a way we can see how many feature requests have requested a certain feature?
How about setting up a voting system where we can see possible new features and how many would benefit from the feature?
It's not encouraging to see multiple "We don't have that feature yet, but it's a popular feature request :)!" comments that are the better part of a decade old.
This feature would allow content architecture discussions with content owners / SMEs, so we can walk through the downstream impact of proposed edits, and discuss whether the logic of a branched scene meets expectations. It also helps with future revisions to a module: revisiting the module and looking at the roadmap helps us determine which content should be refreshed, eliminated, or added, and the feasibility of each type of edit.
Has this feature not been added yet? I see this request started 9 years ago.
Has anyone found a good way to print and show the logic routes, which would be very useful. If I have to produce this for a management overview it will take a long time.
11 Replies
Hi Nathalie,
Not at this time, but it's a popular feature request
Has anything been done on this (6 years later)? I can SNAGIT but there has to be an easy way to print the whole thing. When I am doing branching scenarios, I'd like to be able to scope out the project with temporary blocks and then print it. Please add this feature back to the list if it has somehow disappeared. (even better if it could also be sent to Review) Thanks
Hey Sandra,
Thanks for chiming in to share your thoughts as well.
It hasn't gotten lost, I can still see that this is open with our team. You are obviously using Storyline 360 since you mentioned the use of Review as well, so I'll be sure that this conversation gets added to that report.
Speaking of Review, curious how sending the StoryView to Review would fill a need or use-case for you? I'd like to hear more about that.
is there a timeline for having this feature implemented?
Hi Kelley,
This feature hasn't bubbled up to the top of our roadmap, and that's the point at which we could better identify an ETA, but we're still listening to the feedback! Here's a bit more about how we work to prioritize feature requests.
Just had this request yesterday for a course where you take a quiz question, if correct go to next question; if not get several slides of content. Requestor wanted to show how a competent employee would only see a few slides while others would get topic-specific content. Also wanted to see the draft questions and content at the same time. I got around it by creating each question branch as a separate scene but printing the tree would have been way better.
Thanks for sharing your use-case as well, Steve. I'll add it to our report.
Hi Ashley
Is the roadmap made available to A360 subscribers?
...if not, why not? There are many new apps competing with immersive experiences/features it would be great to be able to share with management what is comping up in future feature releases and this would also assist in convincing my team not to go to another product.
Is there a way we can see how many feature requests have requested a certain feature?
How about setting up a voting system where we can see possible new features and how many would benefit from the feature?
Hi Dearne,
We don’t have a public roadmap, as development and timing can shift.
I shared some information with you here. For others following along, here's how we define bugs and how we tackle them when they occur.
It's not encouraging to see multiple "We don't have that feature yet, but it's a popular feature request :)!" comments that are the better part of a decade old.
This feature would allow content architecture discussions with content owners / SMEs, so we can walk through the downstream impact of proposed edits, and discuss whether the logic of a branched scene meets expectations. It also helps with future revisions to a module: revisiting the module and looking at the roadmap helps us determine which content should be refreshed, eliminated, or added, and the feasibility of each type of edit.
Hi Community
Has this feature not been added yet? I see this request started 9 years ago.
Has anyone found a good way to print and show the logic routes, which would be very useful. If I have to produce this for a management overview it will take a long time.
I hope you can help
Adam