Storyline 2 does not include a rounding results score element. As this thread previously mentioned, a few folks have done so using javascript so you may want to investigate those options.
I am actually running into this issue now. Most of the forum posts and solutions seem to be 3+ years old. Is there an update on this feature request? Am I missing something in Storyline 360?
We haven't changed how this is handled in Storyline 360 yet, so I don't have any updates to share. I know some folks in the E-Learning Heroes community looked at rounding the variables using Javascript. If that's something you're interested in, let us know and then folks in the community can share their tips and expertise.
It is 2021. Surely Articulate should have come up with a simple solution by new. This topic has been ongoing for years. So frustrating to be referred to complex calculations and Java Script.
I completely agree with you. There is a lot of complicated workaround that we have to do because Articulate doesn't listen to its users. I see the score rounding request since Storyline version 1 and still no changes. These are essential functionality for our customers and not frivolous requests. The articulate 360 license is expensive enough to be able to request product improvements and not unnecessary updates like changing a button in the interface.
Crazy that this request is old enough that the non-JS workarounds don't even work anymore because those were leveraging a programming defect in Flash. Why hasn't this been implemented yet?
We appreciate your feedback and understand how this can be frustrating. I wanted to share some information about how we manage these feature requests, as that may be helpful.
We are tracking this feature request and I've adjusted the user impact today as well to reflect another +1 on this.
Much appreciated Kelly. Since there's already a Results.ScorePercent variable stored in the course by default with results slide creation, and that would require a hard-coded math function to happen somewhere in the program to calculate that, I'd expect something like Results.RoundedScorePercent being relatively easy to implement. Here's hoping we beat this one to the 10 year anniversary... :)
Yes, I noted that a popular multiple-trigger workaround to show rounded score % doesn't work any more also. Javascript doesn't preview within Storyline, which makes that workaround slower to test. The 10 year anniversary of this thread for a common feature request is nearing; a 'multiple decimal point' 10 year countdown timer for the fix could be getting closer to around 9.76% by now...
17 Replies
In the past I have used a simple JavaScript with the round() method to do just that; some info onit here: http://www.w3schools.com/jsref/jsref_round.asp. And here is a thread with some info on a non-JavaScript option to round numbers: http://community.articulate.com/forums/p/31583/170723.aspx
Thanks Michael for sharing those here, and Jason, it's a common feature request if you'd like to submit one as well.
Hi, just wondering did this feature ever appear in SL? if so where ;)
Cheers!
Hi Stuart,
Storyline 2 does not include a rounding results score element. As this thread previously mentioned, a few folks have done so using javascript so you may want to investigate those options.
Hello,
I am actually running into this issue now. Most of the forum posts and solutions seem to be 3+ years old. Is there an update on this feature request? Am I missing something in Storyline 360?
Hi Heather,
We haven't changed how this is handled in Storyline 360 yet, so I don't have any updates to share. I know some folks in the E-Learning Heroes community looked at rounding the variables using Javascript. If that's something you're interested in, let us know and then folks in the community can share their tips and expertise.
Is this option available now? It would be nice to have this feature as many of us do not know Javascript.
Hi Maddie!
Great question. Rounding quiz scores isn't a feature in Storyline 360, but you can use triggers to adjust the Results slide variable to round the score. Here's a community post with an option that doesn't include Javascript.
It is 2021. Surely Articulate should have come up with a simple solution by new. This topic has been ongoing for years. So frustrating to be referred to complex calculations and Java Script.
I completely agree with you. There is a lot of complicated workaround that we have to do because Articulate doesn't listen to its users. I see the score rounding request since Storyline version 1 and still no changes. These are essential functionality for our customers and not frivolous requests. The articulate 360 license is expensive enough to be able to request product improvements and not unnecessary updates like changing a button in the interface.
I agree. Requested for over 7 years now and acknowledged in the second response that it's "it's a common feature request".
Crazy that this request is old enough that the non-JS workarounds don't even work anymore because those were leveraging a programming defect in Flash. Why hasn't this been implemented yet?
Hi Joseph,
We appreciate your feedback and understand how this can be frustrating. I wanted to share some information about how we manage these feature requests, as that may be helpful.
We are tracking this feature request and I've adjusted the user impact today as well to reflect another +1 on this.
Much appreciated Kelly. Since there's already a Results.ScorePercent variable stored in the course by default with results slide creation, and that would require a hard-coded math function to happen somewhere in the program to calculate that, I'd expect something like Results.RoundedScorePercent being relatively easy to implement. Here's hoping we beat this one to the 10 year anniversary... :)
Has this one been resolved yet?
Surely 9 years is a good amount of time to come up with a fix?
Do you mean 8.5 years or 9.4999999?
Yes, I noted that a popular multiple-trigger workaround to show rounded score % doesn't work any more also. Javascript doesn't preview within Storyline, which makes that workaround slower to test. The 10 year anniversary of this thread for a common feature request is nearing; a 'multiple decimal point' 10 year countdown timer for the fix could be getting closer to around 9.76% by now...