We've enhanced the branching feature for SOPs. This update resolves previous operational friction points: "It's hard to see where branching is set," "Branching questions force retries on wrong answers," and "Answered questions aren't re-asked on revisit." Read on for details.
① See which steps have branching configured at a glance in the edit screen
You can now visually confirm which steps have branching set across the SOP edit screen. No need to open each question editor one by one to check.
- Before: Branching status was only visible after opening the question editor and entering the branching editor for each step
- Now: Step cards, Group cards, question editor headings, and the branching button all clearly show whether branching is configured
●Key features
- Step card question badge: Steps with branching display as "Question type (Branching)" (example: Multiple choice (Branching))
- Group card: Shows "Question count: N (Branching M)" to indicate how many branching questions are in that group
- Question editor heading: Even when collapsed, the heading displays the "(Branching)" suffix
- "Configure branching" button: When branching is already configured, a "Configured" tag appears on the right
② Branching questions now treated as "route determination" instead of "correct/incorrect quiz"
Branching is fundamentally a route determination that switches which step comes next based on the answer. Previously, it was mixed with question "correct/incorrect" judgments, causing branching questions to force retries on wrong answers or display "error" in the table of contents. This update makes branching questions behave consistently as route determination.
●Specific changes (viewer experience)
- Wrong answer doesn't stop progress: On branching questions, the viewer proceeds to the selected branch. No "incorrect" alert or toast appears
- Correct/incorrect display suppressed: In the question modal and table of contents (Step list), branching questions show as "answered" rather than a correct/incorrect mark
- Re-asked every time even when answered: Since the answer determines the next destination, branching questions are re-asked every time the step is revisited (route determination runs again on revisit)
●Safeguards for editors
- If a question has branching ON and a "correct" answer set, the editor displays a "Caution: Branching is ON, so correct/incorrect judgment is ignored (you will proceed to the branch based on your answer)" notice
- This prevents confusion where branching was intended but the question also behaves as a correct/incorrect quiz
※ Correct/incorrect records are still retained internally, so Usage Report aggregation is unaffected. Only the viewing behavior and display are now consistently structured as route determination.
How to use this
- Inventory branching SOPs: Use the "(Branching)" indicator on step and group cards to quickly identify which steps have branching
- Diagnostic-style SOPs rather than judgment-style: Smoothly guide viewers through branches with no-correct-answer choices like "abnormal/normal" or "Type A/Type B" without forced retries
- SOPs that revisit the same step multiple times: Use re-asking to ensure correct routing on each revisit for cases where current status needs branch determination (loop inspection, status checks)
Thank you for continuing to use Dive◎