What this category's data looks like
This category's data covers three types of materials: the master timetable, the teacher assignment table, and the after-school service project table. Sources are exports from the academic scheduling system, submissions from grade groups, and after-school service receipts. Fields include course name, assigned teacher, class, day and period, date, signature, and receipt status. The update rhythm is set at the start of the semester, fine-tuned within the week, and summarized at the end of the month; changes often occur in class adjustments, substitute teaching, and project additions. When the materials enter workflow orchestration, the master timetable serves as the main record, the teacher assignment table is used to verify teaching assignment relationships, and the after-school service project table is used to verify projects and receipts. In the version ledger, each of the three types of materials plays the role of source evidence, and change records must retain the old version and mark the reference location.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "version ledger and change records" are continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters the interaction state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Fields include course name, class, day and period, date, and signature; determine that the current version is unique and the old version is traceable | Check the options and branch connections one by one in the node, trigger it once to view the node status in the run record, and check that subsequent nodes reference variables and nodeId |
| Teacher assignment table | Fields include assigned teacher, class, course, and date; determine that the name, quantity, and date are consistent with the same record in the master timetable | Reference the selection result variable in a subsequent node and run a trial once, and check whether the name, quantity, and date of the same record in the teacher assignment table and the master timetable match |
| After-school service project table | Fields include project name, number of participants, date, and receipt signature; determine whether the version is not synchronized and whether signatures or receipts are missing | Check the options and branch connections one by one in the node, check whether the name, quantity, and date of the same record in the project table and the master timetable are consistent, and check the receipt signature |
| Version ledger and change records | Determine that the current version is unique, the old version is traceable, and references are synchronized | After changing one piece of content, check whether the version number and references are updated synchronously, and check whether the old version is retained and traceable |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the master timetable and the teacher assignment table. Cause: The two materials were exported or submitted separately and were not compared in the same version ledger.
- Symptom: The version of the after-school service project table is not synchronized, and the old version is still referenced. Cause: After the change, the version number and reference location were not updated, and the old version was not marked as invalid.
- Symptom: The after-school service project table lacks a signature or receipt. Cause: After project additions, signatures were not collected afterward, and receipts were not archived together with the materials.
How to verify the setup
Feature acceptance: Run a trial for each option one by one, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, and that the selection result variable has been passed to subsequent nodes.
Business test: Change one piece of content, see whether the version number and references are updated synchronously, and check whether the name, quantity, and date of the same record in the master timetable, teacher assignment table, and after-school service project table are consistent.
- Check the options and branch connections one by one in the node, trigger it once to view the node status in the run record, and confirm that there is no case where an option is selected but the default branch is still taken, the process stops after the interaction is completed, or the same session repeatedly enters the interaction.
- Reference the selection result variable in a subsequent node and run a trial once, after changing one piece of content check whether the version number and references are updated synchronously, and check that the old version is traceable and signatures and receipts are complete.