What this category's data looks like
The materials on this page come from primary and secondary school timetable and after-school service scheduling scenarios, and include three types: the master timetable, the teacher assignment table, and the after-school service project table. The master timetable is updated weekly, with fields for class, period, course name, assigned teacher, date, and signature column; the teacher assignment table is synchronized weekly, with fields for teacher, class, course, number of class hours, date, and signature; the after-school service project table is updated by project cycle, with fields for project name, participating classes, responsible teacher, number of sessions, date, and receipt. When these three types of materials enter workflow orchestration, the master timetable serves as the main line for progress records, the teacher assignment table is used to verify assignments and class hours, and the after-school service project table is used to verify project session counts and receipts. The update rhythm is intraweek recording and weekend summarization, with signatures and receipts completed as materials move through the process.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "progress table and statistical scope description" is continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters an interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Whether the fields, dates, and signatures are consistent with the teacher assignment table and the after-school service project table | Check class, period, course name, assigned teacher, date, and signature item by item; in the node, check the options and branch connections one by one to confirm the branch direction |
| Teacher assignment table | Whether the assigned teacher and number of class hours match the master timetable and the after-school service project table | Check teacher, class, course, number of class hours, date, and signature; reference variables in subsequent nodes and run a trial once to confirm that the selection result variable has been passed to subsequent nodes |
| After-school service project table | Whether the project name, number of sessions, date, and receipt are consistent with the master timetable and the teacher assignment table | Check project name, participating classes, responsible teacher, number of sessions, date, and receipt; trigger once and inspect the correspondence between node status and nodeId in the run record |
| Progress table and statistical scope description | Whether the number of records and the statistical counts match, and whether the scope is written in the header | Use one week of records to check the totals, and check whether the header scope and exceptions are clearly written; check whether the branch direction and interaction state records are complete |
Three common errors
- Symptom: the name, quantity, or date of the same record do not match between the master timetable and the teacher assignment table. Cause: the two materials are entered separately and are not checked synchronously in the node branch.
- Symptom: the version of the after-school service project table is not synchronized, and the old version is still referenced. Cause: after updating, the user selection node was not triggered again, and the branch still follows the default path.
- Symptom: the master timetable or the after-school service project table lacks a signature or receipt. Cause: when the materials flow to subsequent nodes, the signature column and receipt field are not checked.
How to verify the setup
This feature's acceptance: run trials for each option one by one, and check the branch direction and interaction state in the run record; confirm that each option corresponds to one branch, and reference variables and nodeId in subsequent nodes to check the selection result variable.
Business test: use one week of records to check the totals, and see whether the scope and exceptions are clearly written; check that the number of records and the statistical counts match and that the scope is written in the header.
- In the node, check the options and branch connections one by one, and trigger once to inspect the node status in the run record.
- Reference
variablesin subsequent nodes and run a trial once to confirm that the selection result variable has been passed to subsequent nodes; check the fields, dates, and signatures of the master timetable, teacher assignment table, and after-school service project table.