Data listed in cmi.interactions.x.id

Hi AdityaChettri unfortunately their isn't a cmi.interaction element that you can use to count the users attempt at a question, but Storyline does already change the ID to include the attempt number, but this attempt number is "per session".

For example, a True/False question I have defined with unlimited attempts may record an ID like this if I attempt the question multiple times. I've highlighted the digit at the end of the ID to indicate the attempt:

• Scene1_Slide1_TrueFalse_0_0
• Scene1_Slide1_TrueFalse_0_1
• Scene1_Slide1_TrueFalse_0_2

The problem is, if I then exit the module and then relaunch, and have three more attempts at the question, the ID starts from zero again, and does not continue from 2.

• Scene1_Slide1_TrueFalse_0_0
• Scene1_Slide1_TrueFalse_0_1
• Scene1_Slide1_TrueFalse_0_2

Your LMS would have to be capable of adding all of these up to arrive at a total (6 attempts).

I think the best field to use to track an attempt number might be the cmi.interactions.n.description as Storyline just adds a brief description of the question, and it's a flexible field. For example, for a T/F question, the description is "True or False". 

SetValue('cmi.interactions.3.description', 'True or False')

You could therefore hijack that data field, and log your attempt how you would like to.

SetValue('cmi.interactions.3.description', '{attempt:6}')

The challenge you have with tracking attempts, is keeping track of those attempts, as Storyline does not keep track. You would therefore need a variable for each question, to track the number of attempts the user has had at the question, and use that value.

const player = GetPlayer();
const attempt = player.GetVar('Q1Attempts');
SetValue('cmi.interactions.3.description', `{attempt:${attempt}}`)

This is just a very rough idea, but you would have to hook into the function that is writing the interactions to the LMS and then hijack the part that is writing the description to the LMS. Then you have the challenge of pulling that data from the LMS into a report. That will depend on how much control you have over the LMS and how flexible the reporting tools are.

The function in scormdriver.js that you would have to hijack is SCORM2004_RecordInteraction.

You could assign that function to another function, e.g:

// Assign original function to new function name (allows us to hijack the function)
super_SCORM2004_RecordInteraction = SCORM2004_RecordInteraction
// And then re-define SCORM2004_RecordInteraction so you can override description
function SCORM2004_RecordInteraction(strID, strResponse, blnCorrect, strCorrectResponse, strDescription, intWeighting, intLatency, strLearningObjectiveID, dtmTime, SCORM2004InteractionType){
    // override the strDescription variable
   const player = GetPlayer();
    // You have a global Storyline variable, questionAttempt,  that you set with the current attempt number
   strDescription = `{attempt: ${player.GetVar('questionAttempt')}}`;
   // Call the original function
   return super_SCORM2004_RecordInteraction(strID, strResponse, blnCorrect, strCorrectResponse, strDescription, intWeighting, intLatency, strLearningObjectiveID, dtmTime, SCORM2004InteractionType);
}