What this category's data looks like
This category's data covers three types of materials involved in undergraduate program planning: the program plan, course syllabi, and the credit structure table. The sources are the academic affairs office and the school/department teaching committees, and the update cadence advances in sync with revision batches. The program plan carries the total credits and course modules, the course syllabi correspond to specific course content and assessment methods, and the credit structure table summarizes the credits and proportions of each module. When entering the form input function, the three types of materials each serve as field providers: the program plan provides the major name, revision year, and total credits; the course syllabi provide the course name, course code, and hours/credits; the credit structure table provides the module name, module credits, and proportion. The field characteristic is cross-referencing across multiple materials: the name, quantity, and date of the same record must remain consistent across the three materials, and the version and signature receipt must stay in sync with the batch.
Configuration and implementation checks
| Object | Check | Verification action |
|---|---|---|
| Program of Study | The name, revision year, total credits, and course module fields are complete, and are cross-consistent with the course syllabus and credit structure table | Check the field names one by one in the node configuration, confirm that the program of study fields correspond one-to-one with the material fields to be collected, and check the required markers |
| Course Syllabus | The course name, course code, class hours and credits match the corresponding records in the program of study and credit structure table in name, quantity, and date | Check the field names one by one in the node configuration, confirm that the course syllabus fields correspond one-to-one with the material fields to be collected, and check the required markers |
| Credit Structure Table | The module name, module credits, and proportion are consistent with the corresponding records in the program of study and course syllabus, and the version is synchronized with the signed receipt | Check the field names one by one in the node configuration, confirm that the credit structure table fields correspond one-to-one with the material fields to be collected, and check the required markers |
| Form Fields | The field names correspond one-to-one with the material fields to be collected, and key material fields have been marked as required | Check the field names one by one in the node configuration, check the required settings one by one, and reference the field in subsequent nodes and run a trial |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the program plan and the course syllabi. Cause: The two materials are drafted separately, the fields are not cross-checked, and there is no consistency check before submission.
- Symptom: The version of the credit structure table is not synced and is inconsistent with the program plan revision batch. Cause: The version and date fields are not included in the required markers, and the version number is not checked during drafting and handover.
- Symptom: The handover record lacks a signature or receipt, and the next step cannot sign off. Cause: The responsible person field is not clear, the handover record is not submitted together with the material draft, and the sign-off action is missing.
How to verify the setup
Acceptance of this function: fill in the form once and submit it, and check whether the field values obtained by the subsequent node are consistent with the filled-in content; reference the field in a subsequent node and run a trial to confirm that the field is passed normally after submission, and that the value retrieval paths of formInputResult and selectResult can be checked.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are blocked; check the fields, dates, and signatures of the program plan, course syllabi, and credit structure table to confirm that the responsible person is clear and the version and date are consistent.
- In the node configuration, check the field names and required settings one by one, confirm that the key material fields are marked as required, and that the form cannot be submitted when required items are empty.
- Reference the field in a subsequent node and run a trial to confirm that the field is passed normally after submission and that the conversation does not remain in the interaction state.