Please provide a brief description.
Please make a selection.
Please make a selection.
Please provide a description.
@thomasbleijerveld
Account
Account
The data doesn't fully go through
Hello!
We're using the ClueLabs Data Cloud feature for the assessment of our Articulate courses.
We noticed, that the functionality doesn't work always properly: in some cases, the data doesn't go through, including the score (which should not be possible, because the user even cannot send the message without putting in a score.
That lets us assume that the problem may be not on our side. We are mainly worried, of course, about the absence of a score, but other valuable data also seems not to get through. (Course/Module name, learning type of the lesson).
It has been happening for a relatively long time, and the latest examples are coming during this week.
Would you be kind to take a look at the issue and give us recommendations?
Thank you in advance.
We're using the ClueLabs Data Cloud feature for the assessment of our Articulate courses.
We noticed, that the functionality doesn't work always properly: in some cases, the data doesn't go through, including the score (which should not be possible, because the user even cannot send the message without putting in a score.
That lets us assume that the problem may be not on our side. We are mainly worried, of course, about the absence of a score, but other valuable data also seems not to get through. (Course/Module name, learning type of the lesson).
It has been happening for a relatively long time, and the latest examples are coming during this week.
Would you be kind to take a look at the issue and give us recommendations?
Thank you in advance.
Reply
Posted on 2/22/2024
@support
Hello. Of course. Please upload your .story file and we'll take a look.
Reply
Posted on 2/22/2024
@thomasbleijerveld
Thank you for your reply!
Could you please clarify where exactly I need to upload the file? I don't see the option to attach the file to this conversation. Should that be any third-party resource?
Could you please clarify where exactly I need to upload the file? I don't see the option to attach the file to this conversation. Should that be any third-party resource?
Reply
Posted on 2/22/2024
@support
Yes, you can use any file sharing service (e.g. Dropbox, WeTransfer, Google Drive, etc.) and simply post the link in a response here.
Reply
Posted on 2/22/2024
@thomasbleijerveld
Awesome, thank you.
Here's the example: [LINK]
The assessment was sent on February, 19th, but only the course name, module name, and update number got through.
Please let me know if you need more examples or additional information.
Here's the example: [LINK]
The assessment was sent on February, 19th, but only the course name, module name, and update number got through.
Please let me know if you need more examples or additional information.
Reply
Posted on 2/23/2024
@support
Hello. Here are a few obvious issues in this file:
- The first JavaScript trigger that loads the widget should not be on the layer inside the secondary master, it should be on the main master slide and should execute as soon as possible when the module starts to ensure that when you're ready to send the data, the widget has already loaded. Storyline does not wait for javascript code to finish executing before proceeding to the next trigger, so there is a scenario when you can click Send before the widget loads with the current setup.
- Consider what happens after the person clicks Send. Will they close the module? The Send trigger has 20 separate pieces of data to send, so even if each takes just 1 second, is the person going to wait for 20 seconds after clicking Send? If not, the browser will interrupt the code execution on window close or on navigating away, which will mean that some pieces of data will not be sent.
- One way you can work with a lot of data is to utilize the variable stencilrendered. Each time you save one piece of data, this variable will increase by 1. So you can set stencilrendered to 0 before sending, then show a layer asking the user to wait until the operation finishes, and have a trigger that checks stencilrendered every time it changes. When the value of stencilrendered is finally 20, you can hide the waiting layer and let the user know that the feedback was submitted. This, of course, does not guarantee that they will wait, but it does make it more likely that they will.
- If you don't want to utilize stencilrendered, you can try saving some data right away when the pop-up first opens. Things like product name, course name, module name, etc. seem like something that will not change based on the user input on the layer, so it should be okay to save them right away. So by the time the user clicks Send, most of this static information will already be sent.
- The first JavaScript trigger that loads the widget should not be on the layer inside the secondary master, it should be on the main master slide and should execute as soon as possible when the module starts to ensure that when you're ready to send the data, the widget has already loaded. Storyline does not wait for javascript code to finish executing before proceeding to the next trigger, so there is a scenario when you can click Send before the widget loads with the current setup.
- Consider what happens after the person clicks Send. Will they close the module? The Send trigger has 20 separate pieces of data to send, so even if each takes just 1 second, is the person going to wait for 20 seconds after clicking Send? If not, the browser will interrupt the code execution on window close or on navigating away, which will mean that some pieces of data will not be sent.
- One way you can work with a lot of data is to utilize the variable stencilrendered. Each time you save one piece of data, this variable will increase by 1. So you can set stencilrendered to 0 before sending, then show a layer asking the user to wait until the operation finishes, and have a trigger that checks stencilrendered every time it changes. When the value of stencilrendered is finally 20, you can hide the waiting layer and let the user know that the feedback was submitted. This, of course, does not guarantee that they will wait, but it does make it more likely that they will.
- If you don't want to utilize stencilrendered, you can try saving some data right away when the pop-up first opens. Things like product name, course name, module name, etc. seem like something that will not change based on the user input on the layer, so it should be okay to save them right away. So by the time the user clicks Send, most of this static information will already be sent.
Reply
Posted on 2/23/2024
@thomasbleijerveld
Thank you for your investigation!
We'll try to apply your recommendations and see if it helps.
We'll try to apply your recommendations and see if it helps.
Reply
Posted on 2/23/2024