What this category's data looks like
This page addresses the course selection and scheduling and classroom resource scheduling category; the materials cover three types: course offering plans, scheduling tables, and course selection rules. Course offering plans come from the academic affairs department and are updated by semester; the fields include course name, class, number of students, instructor, start and end dates, and a signature field. Scheduling tables are maintained weekly by the scheduling role; the fields include classroom number, time slot, course name, week number, and review signature. Course selection rules are published by the teaching and research group each course selection season; the fields include applicable grade, selectable courses, quota, and effective date. When these three types of materials enter the form input node, each plays a different role: the course offering plan determines the range of selectable courses, the scheduling table determines classroom and time slot occupancy, and the course selection rules determine the course selection scope visible to the visitor. In terms of field characteristics, the same course's name, number of students, and dates in the course offering plan and the scheduling table must be consistent, versions must be synchronized, and signatures or receipts must be complete.
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 externally available entry point and authorization scope are then completed by subsequent nodes or manually. 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 |
|---|---|---|
| Course offering plan | Course name, class, number of students, start and end dates, and signature field must be aligned item by item with the scheduling table | Check the field names one by one in the node configuration, and check whether the required markers cover the key fields |
| Scheduling table | Classroom number, time slot, week number, and review signature must be consistent with the course offering plan, and versions must be synchronized | Reference this field in a subsequent node and run a test to confirm that the field value can be retrieved after submission |
| Course selection rules | Applicable grade, selectable courses, quota, and effective date must be consistent with the course offering plan; if a signature or receipt is missing, it must not be released | Access once with a restricted identity, and check whether the visible scope matches the rule settings |
| Form fields | Field names correspond one-to-one with the material fields to be collected, and key fields are marked as required | Check the required settings one by one, and confirm that submission is impossible when a required item is empty |
Three common errors
- Symptom: The same course's name, number of students, and dates do not match between the course offering plan and the scheduling table. Cause: The two materials are maintained separately, without item-by-item comparison and version synchronization.
- Symptom: After the scheduling table is updated, the course selection rules are still the old version. Cause: Versions are not synchronized, and the publishing step lacks receipt confirmation.
- Symptom: The course offering plan enters circulation without a signature or receipt. Cause: The required markers do not cover the signature field, and subsequent nodes cannot retrieve the value after submission.
How to verify the setup
Acceptance for this feature: fill it out once and submit, check the field values retrieved by subsequent nodes, and confirm that the formInput output is consistent with the userSelect selection items.
Business test: access once with a restricted identity, see whether the visible scope matches the settings, and confirm that unauthorized content is not visible.
- Check the field names and required markers one by one in the node configuration, and confirm that the key material fields are marked as required.
- Reference the
formInputResultandselectResultfields in subsequent nodes and run a test to confirm that the field values can be retrieved after submission.