What this category's data looks like
This page addresses the scenario of primary and secondary school timetables and after-school service scheduling. The materials come from three types of source tables: the academic affairs office's master timetable, the teacher assignment table, and the after-school service project table. They circulate on a rhythm of being set at the start of the semester, fine-tuned weekly, and updated at any time for temporary schedule changes. The master timetable records class, period, week, and venue; the teacher assignment table records teacher, subject, class, and number of class hours; the after-school service project table records project name, participating classes, number of participants, time slot, and responsible teacher. When these three types of materials enter the form input step, each plays its own role as a field source: the master timetable provides time and venue fields, the assignment table provides personnel and class-hour fields, and the project table provides project and participant-count fields, together supporting a draft material that can be issued and a handover record.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, and outputs the field values filled in by the user (passed to subsequent nodes after submission). The "draft material that can be issued and handover record" is completed by subsequent nodes or manually afterward. The form input node does not automatically identify material content, nor does it judge whether the material is authentic.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Fields include class, period, week, and venue; the date and version number must be consistent with the assignment table | Check the field names one by one in the node configuration, and confirm that the required markers cover class and period |
| Teacher assignment table | Fields include teacher, subject, class, and number of class hours; the quantity and names must match the master timetable | Check the required settings one by one, and after a trial run check whether subsequent nodes can retrieve the teacher and class-hour field values |
| After-school service project table | Fields include project name, participating classes, number of participants, time slot, and responsible teacher; signatures and receipts must be complete | Reference this field in a subsequent node and run a trial, and check that the project name and number of participants are consistent with the master timetable records |
| Handover record | The three items of responsible person, version, and date must be clear and consistent with the attached materials | Configure the fields with formInputResult and selectResult and run a trial, and confirm that the fields are passed normally after submission |
Three common errors
- Symptom: the name or number of participants for the same class does not match between two materials. Cause: the field source was not unified during drafting, and each table was entered separately without cross-checking.
- Symptom: the material version is not synchronized, and an old timetable is mixed with a new project table. Cause: the update rhythms are not synchronized, and the version number and date were not recorded at handover.
- Symptom: the handover lacks a signature or receipt, and the responsible person is unclear. Cause: the form did not set the signature and receipt as required, and no one confirmed receipt after submission.
How to verify the setup
This feature's acceptance: fill out the form once and submit it, then check whether the field values retrieved by subsequent nodes are consistent with what was filled in, focusing on the output of formInputResult and selectResult.
Business test: draft one copy according to the template and complete one handover, see whether missing items are blocked, and confirm that the responsible person, version, and date are consistent.
- Check the field names and required markers one by one in the node configuration, and confirm that key material fields are marked as required.
- Reference the form fields in subsequent nodes and run a trial, and confirm that the corresponding field values can be retrieved after submission and that the conversation does not get stuck in the interaction state.