In the final stages of rolling out a huge onboarding training (12 eLearning units) my testers are discovering that they can't go "back" and then forward again. They get stuck, only having the PREV button available to them.
I've set all my slides to "Resume Saved State" but when they click back to the previous slide, last layer (where the the trigger was set to change NEXT to "Normal") it isn't there.
Hi, Erin -- Thanks so much for your patience, and if you click on this link for your published output on tempshare.articulate.com, you will see that I also encountered the same behavior you have described. I feel that additional investigation by our Support Engineers could be beneficial, so I will go ahead and submit a case request for you. You will be hearing from a member of that staff just as soon as possible, and I intend to share relevant updates here in the thread for others who may benefit! :)
Thanks Christie... It's strange, but all of my courses are acting the same! (Quite frustrating as this is the first major training project I'm producing for my company)
I've received the email from Justin at Articulate Support. Thank you for your help!
Excellent, Erin! I just wanted to let you know that I see your ticket #00730217 has been received and one of our amazing Support Engineers will be on the case before you know it! Thanks for your patience and I'll be sure to stay in the loop on their progress, as well! :)
Hi, Erin -- Just wanted to touch base with you, as I see our Support Engineer, Eloisa, reached out to request your file in your case #00730217 on 1/22/16 around 7 pm.
If for some reason you did not receive her message, please check your SPAM folder to see if it was rerouted there in error, and I will continue to monitor the progress being made on your issue. :)
So glad to hear it, Erin, and I'm glad you were able to locate the wandering email! I did want to confirm that your uploaded files were received this morning shortly after 9 am, so thanks again for your patience, and Eloisa will be in touch via email as soon as possible. :)
After some back-and-forth, they figured out that this is indeed an issue, as they were able to duplicate the issue. In the meantime, if others are struggling with this problem, there are a few options:
We have reviewed this and we were able to duplicate your issue. I have submitted your case to our Quality Assurance team for their review. As a workaround you can try using variables as condition for the button states. Please see the following options below:
Option1 (as what I previously did on your .story file): 1) Create T/F variable and set initial value to false 2) Add trigger to Change state of Next button to Hidden on base layer when timeline starts 3) Add trigger to Change state of Next button to Normal on base layer when variable is true 4) On slide layer or button click, add trigger to Set variable to true 5) On slide layer, add trigger to Change state of Next button to Normal when variable is true
Option2: 1) Create T/F variable and set initial value to false 2) Add trigger to Change state of Next button to Hidden on base layer when variable is false 3) On slide layer or button click, add trigger to Set variable to true 4) On slide layer, add trigger to Change state of Next button to Normal
That is excellent, Erin, and I appreciate that you were able to share the information provided by our Support staff here in the thread (you beat me to it)! Please let us know if there is anything more we can do to assist. :)
10 Replies
Hi, Erin -- Are you seeing the same behavior when testing in the intended environment? Please share your file so we can take a closer look for you.
They are testing it in the published site, and I'm seeing the same behaviour in the SL preview.
Here's the live link: http://elearn.vpi-inc.com/AA_Unit08_KeyTags/story.html (works best in Chrome)
And the file is attached...
Thank you!
Hi, Erin -- Thanks so much for your patience, and if you click on this link for your published output on tempshare.articulate.com, you will see that I also encountered the same behavior you have described. I feel that additional investigation by our Support Engineers could be beneficial, so I will go ahead and submit a case request for you. You will be hearing from a member of that staff just as soon as possible, and I intend to share relevant updates here in the thread for others who may benefit! :)
Thanks Christie... It's strange, but all of my courses are acting the same! (Quite frustrating as this is the first major training project I'm producing for my company)
I've received the email from Justin at Articulate Support. Thank you for your help!
Excellent, Erin! I just wanted to let you know that I see your ticket #00730217 has been received and one of our amazing Support Engineers will be on the case before you know it! Thanks for your patience and I'll be sure to stay in the loop on their progress, as well! :)
Hi, Erin -- Just wanted to touch base with you, as I see our Support Engineer, Eloisa, reached out to request your file in your case #00730217 on 1/22/16 around 7 pm.
If for some reason you did not receive her message, please check your SPAM folder to see if it was rerouted there in error, and I will continue to monitor the progress being made on your issue. :)
Hi Christie
My apologies for not replying... The email did in fact get lost. I am uploading my files now. Thanks for staying in touch!
So glad to hear it, Erin, and I'm glad you were able to locate the wandering email! I did want to confirm that your uploaded files were received this morning shortly after 9 am, so thanks again for your patience, and Eloisa will be in touch via email as soon as possible. :)
Hi there!
After some back-and-forth, they figured out that this is indeed an issue, as they were able to duplicate the issue. In the meantime, if others are struggling with this problem, there are a few options:
We have reviewed this and we were able to duplicate your issue. I have submitted your case to our Quality Assurance team for their review. As a workaround you can try using variables as condition for the button states. Please see the following options below:
Option1 (as what I previously did on your .story file):
1) Create T/F variable and set initial value to false
2) Add trigger to Change state of Next button to Hidden on base layer when timeline starts
3) Add trigger to Change state of Next button to Normal on base layer when variable is true
4) On slide layer or button click, add trigger to Set variable to true
5) On slide layer, add trigger to Change state of Next button to Normal when variable is true
Option2:
1) Create T/F variable and set initial value to false
2) Add trigger to Change state of Next button to Hidden on base layer when variable is false
3) On slide layer or button click, add trigger to Set variable to true
4) On slide layer, add trigger to Change state of Next button to Normal
Hope this helps anyone else! :)
That is excellent, Erin, and I appreciate that you were able to share the information provided by our Support staff here in the thread (you beat me to it)! Please let us know if there is anything more we can do to assist. :)
This post was removed by the author
This discussion is closed. You can start a new discussion or contact Articulate Support.