few months ago I discovered a bug but, so far, no solution has been deployed despite my multiple requests to speed up the process. Indeed if you are using a numeric variable with decimals it happens that the value is rounded if the player has the feature Resume on restart active.
I post this to inform all of you hoping that Articulate can find a solution as fast as possible. The case is the 01899822. If you are experiencing the same issue please refers to it.
This may not be related, there is a known issue that for a variable value to be saved for resume you must jump slides I believe this is expected behaviour rather than a bug.
Hi Dave, well I am really surprized by the fact that this issue was already notified 7 years ago...I didin't realized that when I published my post. It is really a pity.
We are paying a licence and we should get a fix in a reasonable period of time especially when a bug is discovered. 7 years to apply a fix to something that must work in a proper way doesn't fall in the "reasonable" definition. Frankly speaking I don't care about the policy of Articulate to apply fix only when there is a big volume of designers notifying an issue.
No question about the new trigger features widely described...but if we can't rely on the basic mechanism to make triggers working than it is clear that I am also disappointed.
I really hope that someone will find a solution asap
I understand the gravity of this issue and so does our team! As you've seen here, our team is intentional about every fix and feature we release. One of the many reasons for this decision is to ensure every release is met with perfection and impact.
Our team has begun investigating this bug and started the process to release the fix. When we are ready to share, I'll report back to this discussion!
I submitted a support case quoting your reference 01899822 on 25/11/2019. Hopefully there is a fix soon.
Due to my project deadline being yesterday I used a work around (using triggers to calculate the amounts to two decimal places from saved variables that didn't use decimal places).
For your information: I submitted a similar support case a few days ago, and customer support pointed out that this issue is resolved in version 3.36.21213.0 and later. A quick test confirms this, though the value still seems to be rounded to 2 decimals.
13 Replies
Not a problem I've personally run into (yet) but I'll be following this thread to see if it gets resolved.
How is it getting rounded?
Hi
here is the process
a) create a numeric variable with an initial value of 45.50 (i.e)
b) create an interaction that deducts 0.25
c) activate the feature Resume on restart in the player
d) publish the course
e) enter the course, play with the interaction
f) close the course and restart
The displayed value of the variable is not as the one generated before closing the course.
This may not be related, there is a known issue that for a variable value to be saved for resume you must jump slides I believe this is expected behaviour rather than a bug.
Sent from my iPhone
You are right, I forgot to mention that after the interaction you must jump to another slide.
The variable not saving unless you jump slides is expected behaviour rather than a bug.
Sent from my iPhone
I'm having the same issue.
Resuming a course via prompt removes numerical value after the decimal. e.g. the numeric value 37.5 becomes 37 on restart.
Looks like the same bug behaviour was mentioned 7 years ago!
https://community.articulate.com/discussions/articulate-storyline/numeric-data-entry-field-and-course-resume
This is quite problematic. Any news of a fix?
Hi Dave, well I am really surprized by the fact that this issue was already notified 7 years ago...I didin't realized that when I published my post. It is really a pity.
We are paying a licence and we should get a fix in a reasonable period of time especially when a bug is discovered. 7 years to apply a fix to something that must work in a proper way doesn't fall in the "reasonable" definition. Frankly speaking I don't care about the policy of Articulate to apply fix only when there is a big volume of designers notifying an issue.
No question about the new trigger features widely described...but if we can't rely on the basic mechanism to make triggers working than it is clear that I am also disappointed.
I really hope that someone will find a solution asap
Hi Dave and Andrea!
I understand the gravity of this issue and so does our team! As you've seen here, our team is intentional about every fix and feature we release. One of the many reasons for this decision is to ensure every release is met with perfection and impact.
Our team has begun investigating this bug and started the process to release the fix. When we are ready to share, I'll report back to this discussion!
Dear Lauren
Cool, I am expecting the fix as Xmas gift :-)
Good luck with everything Andrea.
I submitted a support case quoting your reference 01899822 on 25/11/2019. Hopefully there is a fix soon.
Due to my project deadline being yesterday I used a work around (using triggers to calculate the amounts to two decimal places from saved variables that didn't use decimal places).
This post was removed by the author
Thanks Lauren
For your information: I submitted a similar support case a few days ago, and customer support pointed out that this issue is resolved in version 3.36.21213.0 and later. A quick test confirms this, though the value still seems to be rounded to 2 decimals.
This discussion is closed. You can start a new discussion or contact Articulate Support.