What this category's data looks like
This page addresses primary and secondary school timetable and after-school service scheduling scenarios. The materials come from three types of forms—the master timetable, the teacher assignment table, and the after-school service project table—as well as deployment status records and operation logs. The master timetable provides class, date, and course name; the teacher assignment table provides teacher name, assigned class, and period; the after-school service project table provides project name, number of participants, and responsible teacher. The update cadence changes weekly or per semester, and the field characteristics are mainly dates, names, quantities, and signature fields. When entering workflow orchestration, the three types of forms serve as the basis for branch decisions and the working draft for handover verification, while deployment status and operation records serve as reference materials for consistency between versions and task records, jointly supporting item-by-item verification of the handover form.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Handover-ready deployment status and operation records" are then completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Fields include class, date, course name, and signature field; when compared with the teacher assignment table and the after-school service project table, names, quantities, and dates must be consistent, and versions must be synchronized | Verify item by item the class, date, and course name in the master timetable against the teacher assignment table and the after-school service project table; check whether signatures or receipts are complete; view the node status corresponding to nodeId in the run records |
| Teacher assignment table | Fields include teacher name, assigned class, period, and signature field; the names, quantities, and dates of the same record in the two materials must match, and versions must be synchronized | Check teacher name, assigned class, and period against the master timetable and the after-school service project table; check signatures or receipts; reference variables in a subsequent node and run a trial once |
| After-school service project table | Fields include project name, number of participants, responsible teacher, and signature field; when compared with the master timetable and the teacher assignment table, names, quantities, and dates must be consistent, and versions must be synchronized | Verify item by item the project name, number of participants, and responsible teacher against the master timetable and the teacher assignment table; check signatures or receipts; trigger a user selection node once and view the branch direction and interaction status in the run records |
| Deployment status and operation records | Version, connection, and task records must be consistent; the names, quantities, and dates of the same record in the two materials must match; missing signatures or receipts are considered incomplete | Verify item by item the version number, connection status, and task records according to the handover form; check whether variables have been passed to subsequent nodes; confirm that the branch direction and interaction status records are complete |
Three common errors
- Symptom: The names, quantities, and dates of the same record in the master timetable and the teacher assignment table do not match. Cause: The two materials were updated separately without cross-verification.
- Symptom: Versions are not synchronized, and the deployment status and operation records point to different batches. Cause: Versions and task records were not registered uniformly after updates.
- Symptom: Signatures or receipts are missing, and an item in the handover form has no record. Cause: The signature fields and receipts were not verified item by item during handover.
How to verify the setup
This feature's acceptance: trial-run each option one by one, and check the branch direction and interaction status in the run records; reference variables in a subsequent node to confirm that the selection result has been passed; use nodeId to locate the node status.
Business testing: verify item by item once according to the handover form to see which record is missing; compare the names, quantities, dates, and signatures of the master timetable, teacher assignment table, and after-school service project table, and confirm that version, connection, and task records are consistent.
- In the user selection node, verify the options and branch connections one by one, trigger it once, and then view the node status and branch direction in the run records.
- Reference the selection result variable in a subsequent node and run a trial once, while verifying the names, quantities, dates, and signatures of the master timetable, teacher assignment table, and after-school service project table according to the handover form.