Issue with cmi.interaction data when published as SCORM 1.2

Thanks Steven - it is one character per response (in terms of the options). In a test example (using generic text for options e.g. 'Option A', 'Option B'). 

Published as SCORM 1.2 I get this:

• cmi.interactions.0.id: Scene1_QuestionDraw11_Slide8_MultiChoice_0_0
• cmi.interactions.0.type: Choice
• cmi.interactions.0.objectives.0.id: Assesment_01_Scorm_1.2_
• cmi.interactions.0.timestamp: 2024-11-19T14:44:58
• cmi.interactions.0.correct_responses.0.pattern: o
• cmi.interactions.0.weighting: 10
• cmi.interactions.0.learner_response: o
• cmi.interactions.0.result: correct
• cmi.interactions.0.latency: 0000:00:16.50
• cmi.interactions.0.description:

Whereas when published as SCORM 2004 I get:

• cmi.interactions.3.id: Scene1_QuestionDraw11_Slide8_MultiChoice_0_0
• cmi.interactions.3.type: Choice
• cmi.interactions.3.objectives.0.id: Assesment_01_scorm_2004
• cmi.interactions.3.timestamp: 2024-11-19T17:22:59
• cmi.interactions.3.correct_responses.0.pattern: Option_B
• cmi.interactions.3.weighting: 10
• cmi.interactions.3.learner_response: Option_B
• cmi.interactions.3.result: correct
• cmi.interactions.3.latency: 0000:00:27.35
• cmi.interactions.3.description: Question 8 text

So it looks like the the option responses ('correct_responses' and 'learner_response') are being shortened (and case changed) from 'Option_B' to 'o'.

The real course features client IP that I can't share but I will send over a generic / test example .story file to Articulate support to see if they can identify the issue.

Many thanks

Conor