What this category's data looks like
This category's data consists mainly of student registration forms, teaching plans, and skills training records, sourced from routine reporting by academic affairs and departments, with an update cadence that advances along semester registration, teaching weeks, and skills training milestones. Student registration forms carry student identity, registration date, and signature fields; teaching plans carry course names, credit-hour counts, and version dates; skills training records carry training items, completion counts, and instructor signatures. When these three types of materials enter the Q&A intake and missing-item follow-up function, student registration forms are used to verify identity and registration status, teaching plans are used to verify courses and versions, and skills training records are used to verify training completion and signature receipts. Field characteristics center on names, counts, dates, and signatures, and missing items often manifest as key fields left blank, versions not synchronized, or receipts absent.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "Intake records and items to be completed" are continued and completed by subsequent nodes according to the branches. When a node is triggered, the conversation enters an interaction state; after the user completes a selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| User selection node | Each option corresponds to one branch; options and branch connections are checked one by one | In the node, check options and branch connections one by one; after a trial run, inspect the branch directions and interaction states in the run records, and confirm the correspondence between nodeId and variables |
| Student registration form | Whether fields, dates, and signatures are complete, and whether registration status is consistent with the teaching plan | Check the registration date, signature field, and receipt; confirm whether missing items are identified and followed up on, and whether the follow-up items reference the selection results in variables |
| Teaching plan | Whether course names, credit-hour counts, and version dates match the skills training records | Compare the names, counts, and dates of the same course in the two materials, and confirm whether a follow-up occurs when the version is not synchronized |
| Skills training record | Whether training items, completion counts, and instructor signatures are complete | Check the training counts and signatures, and confirm whether a follow-up occurs before answering when a signature or receipt is missing |
Three common errors
- Symptom: The names, counts, and dates of the same record do not match between the student registration form and the teaching plan. Cause: The two materials are reported separately, without field-level comparison and version synchronization.
- Symptom: The teaching plan version is not synchronized, and an old course version is still referenced. Cause: The version date does not advance with updates, and version differences are not identified at intake.
- Symptom: A skills training record is missing a signature or receipt but still proceeds to subsequent processing. Cause: Missing-item identification does not cover the signature field, and the follow-up branch is not triggered.
How to verify the setup
This function's acceptance: run trials option by option, check the branch directions and interaction states in the run records, confirm that options and branches correspond one to one, that the selection result variable has been passed to subsequent nodes, that subsequent nodes reference this variable and are trial-run once, and check the transfer of nodeId and variables.
Business test: submit a question missing key information and see whether a follow-up occurs before answering, and whether the follow-up items cover names, counts, dates, and signatures.
- In the user selection node, check options and branch connections one by one, and confirm that each option corresponds to one branch.
- In subsequent nodes, reference the selection result variable and trial-run once, and check the node states and branch directions in the run records.