What this category's data looks like
This page addresses the scenario of primary and secondary school timetables and after-school service scheduling, handling three types of materials: the master timetable, the teacher assignment table, and the after-school service project table. The master timetable comes from academic affairs consolidation, updated at the beginning of each semester and during schedule adjustment weeks, with fields including class, period, course name, assigned teacher, week number, version number, and issuer; the teacher assignment table comes from each grade group, updated according to personnel changes and substitute arrangements, with fields including teacher name, assigned class, subject, weekly class hours, effective date, and signature column; the after-school service project table comes from joint reporting by moral education and logistics, updated monthly and by project cycle, with fields including project name, participating grades, number of participants, venue, time slot, responsible person, and receipt column. When these three types of materials enter workflow orchestration, the master timetable serves as the baseline reference, the teacher assignment table serves for personnel and class-hour verification, and the after-school service project table serves for time-slot and venue coordination, each circulating in two forms: draft and handover record.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Signable material drafts and handover records" are then completed by subsequent nodes continuing execution along the branches. When a node is triggered, the conversation enters an interactive state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the chosen option.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Fields including class, period, course name, assigned teacher, week number, version number, and issuer are complete; date and signature are consistent | Check fields and signature column item by item, run a trial to see the branch direction, and confirm node status in the run record |
| Teacher assignment table | Teacher name, assigned class, subject, weekly class hours, effective date, and signature column are complete; the name, quantity, and date match the same record in the master timetable | Reference variables in subsequent nodes and run a trial, checking the name and class hours of the same record in both materials |
| After-school service project table | Project name, participating grades, number of participants, venue, time slot, responsible person, and receipt column are complete; version and date are synchronized | Check the receipt and signature, verify whether the version number is synchronized, and confirm that the branch corresponding to nodeId has been recorded |
| Handover record | Responsible person is clear, version and date are consistent, signature and receipt are complete, and there are no missing fields | Draft one according to the template and complete one handover, see whether missing fields are blocked, and check nodeId and variables |
Three common errors
- Symptom: The name and quantity of the same record do not match between the master timetable and the teacher assignment table. Cause: The two materials are reported separately, and fields are not checked against the same baseline.
- Symptom: The version of the after-school service project table is not synchronized, and the date is inconsistent with the master timetable. Cause: The update rhythms differ, and the version number and effective date are not checked during handover.
- Symptom: The handover record lacks a signature or receipt, and the next step cannot be signed for. Cause: The responsible person is not clear, and the draft is not checked item by item according to the template.
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 check whether variables and nodeId are passed along with the branch.
Business test: Draft one according to the template and complete one handover, and see whether missing fields are blocked.
- In the node, check the options and branch connections one by one, and trigger once to view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once, checking the name, quantity, date, and signature receipt of the same record in both materials.