What this category's data looks like
This page focuses on the category of primary and secondary school timetables and after-school service scheduling. The source materials are the master timetable exported from the academic affairs system, the teacher assignment table, the after-school service project table, and receipt slips. The update cadence changes on a rolling basis with scheduling at the start of the semester, midweek schedule adjustments, and additions to after-school service projects. Field characteristics center on course name, assigned teacher, class, week number, period, project name, service date, number of participants, and signature field. The three types of materials play different roles when entering this feature: the master timetable provides the baseline for classes and periods, the teacher assignment table provides the correspondence between personnel and subjects, the after-school service project table provides the basis for projects and service dates, and the receipt and signature field are used to confirm whether the responsible party has been informed of the exception.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, which outputs the field values filled in by the user (passed to subsequent nodes after submission). The exception list and review conclusion are completed by subsequent nodes or manually afterward. After the form input node is triggered, the conversation enters an interactive state and records the workflow state. After the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Class, period, week number, and course name must correspond item by item with the teacher assignment table, and the date and signature field must not be blank | Check the field names one by one in the node configuration, confirm that the master timetable fields correspond one-to-one with the form fields, and check the required settings |
| Teacher assignment table | The assigned teacher, subject, and number of classes must be consistent in the two materials, and the version number must be synchronized with the current semester | Reference the formInputResult field in subsequent nodes and run a test to confirm that the teacher and subject field values can be retrieved after submission |
| After-school service project table | The project name, service date, number of participants, and receipt signature must match the master timetable and teacher assignment table | Check the required markers one by one, confirm that the project name and service date are marked as required, and submission must not be allowed when the signature or receipt is missing |
formInputResult and selectResult | Field values must be able to be passed to subsequent nodes, and the options must cover exception types and review conclusions | Reference the formInputResult and selectResult fields in subsequent nodes and run a test to confirm that the corresponding values can be retrieved |
Three common errors
- Symptom: the name of the same course does not match between the master timetable and the teacher assignment table. Cause: the two tables are maintained by different personnel, the naming standard is not unified, and no item-by-item comparison was made before submission.
- Symptom: the service date in the after-school service project table is misaligned with the week number in the master timetable. Cause: the version was not synchronized, the old project table is still in circulation, and the form did not check the version number.
- Symptom: the review conclusion lacks a signature or receipt. Cause: the required marker does not cover the signature field, and after submission subsequent nodes cannot retrieve the signature field value.
How to verify the setup
Feature acceptance: fill it out once and submit, check the field values retrieved by subsequent nodes, confirm that both the formInputResult and selectResult fields can be passed, and that submission is not allowed when required items are empty.
Business test: create an exception record, see whether the source material can be traced, and check whether the fields, dates, and signatures of the master timetable, teacher assignment table, and after-school service project table support the exception.
- Check the field names one by one in the node configuration, confirm that the form fields correspond one-to-one with the fields of the master timetable, teacher assignment table, and after-school service project table, and check the required settings.
- Reference the
formInputResultandselectResultfields in subsequent nodes and run a test to confirm that the corresponding field values can be retrieved after submission, and that the conversation does not remain in the interactive state.