Troubleshooting Decision Path

// Troubleshooting Decision Path starter logic for Articulate Storyline
// Suggested trigger: Execute JavaScript after learner completes the final step

const player = GetPlayer();

const signalChoice = player.GetVar("signalChoice");
const checkChoice = player.GetVar("checkChoice");
const actionChoice = player.GetVar("actionChoice");

const pathKey = `${signalChoice}_${checkChoice}_${actionChoice}`;

const pathProfiles = {
  "field_mismatch_compare_context_decision_aid": {
    diagnosis: 96,
    efficiency: 92,
    support: 95,
    tone: "Exactly",
    title: "Strong troubleshooting path",
    body: "This path identifies the real-world mismatch, checks where the documented flow breaks down, and gives the learner a practical decision aid. It supports action without ignoring the system issue.",
    recommendedAction: "Provide the decision aid and document the mismatch for content or product review."
  },
  "field_mismatch_compare_context_escalate_with_context": {
    diagnosis: 94,
    efficiency: 78,
    support: 88,
    tone: "Strong",
    title: "Good escalation with useful context",
    body: "This path works well when the mismatch may affect other learners or indicates that the documented flow is outdated. The escalation is stronger because it includes the exact point of failure.",
    recommendedAction: "Escalate with screenshots, learner language, and the step where the flow diverged."
  },
  "unclear_instruction_repeat_module_full_restart": {
    diagnosis: 58,
    efficiency: 30,
    support: 42,
    tone: "Not exactly",
    title: "This may be too heavy",
    body: "Restarting the full experience may create frustration if the learner only needs one unclear instruction clarified. A lighter support moment would likely be more useful.",
    recommendedAction: "Clarify the confusing instruction and provide a short example."
  },
  "tech_failure_skip_check_escalate_with_context": {
    diagnosis: 82,
    efficiency: 76,
    support: 84,
    tone: "Cautious",
    title: "Escalation may be appropriate",
    body: "If this is truly a technical failure, escalation can be the right move. The key is to include enough context so the next team can act instead of restarting the investigation.",
    recommendedAction: "Capture device, screen, step, error language, and what the learner already tried."
  }
};

const fallbackProfiles = {
  decision_aid: {
    diagnosis: 78,
    efficiency: 84,
    support: 88,
    tone: "Useful",
    title: "Useful support path",
    body: "A decision aid can help the learner continue without overloading the moment. Make sure the aid is tied to the actual signal, not just a generic reminder.",
    recommendedAction: "Create a short field-ready guide for the specific condition."
  },
  escalate_with_context: {
    diagnosis: 74,
    efficiency: 66,
    support: 78,
    tone: "Cautious",
    title: "Escalation needs context",
    body: "Escalation can be useful, but only if the learner or support team captures the right details. Without context, escalation just moves confusion to another team.",
    recommendedAction: "Document the exact mismatch before escalating."
  },
  full_restart: {
    diagnosis: 46,
    efficiency: 28,
    support: 36,
    tone: "Redirect",
    title: "Avoid restarting by default",
    body: "Sending someone back through a full experience can feel like punishment if they only need targeted help. Use full restart only when the foundation is clearly missing.",
    recommendedAction: "Use targeted support before assigning a full restart."
  }
};

const profile = pathProfiles[pathKey] || fallbackProfiles[actionChoice] || fallbackProfiles.decision_aid;

player.SetVar("troubleshootingPath", pathKey);
player.SetVar("diagnosisScore", profile.diagnosis);
player.SetVar("efficiencyScore", profile.efficiency);
player.SetVar("supportFitScore", profile.support);
player.SetVar("feedbackTone", profile.tone);
player.SetVar("feedbackTitle", profile.title);
player.SetVar("feedbackBody", profile.body);
player.SetVar("recommendedAction", profile.recommendedAction);