What this category's data looks like
This category's data covers three types of materials: program plans, course syllabi, and credit structure tables. The sources are the academic affairs system and revision drafts submitted by departments, and the update cadence rolls by academic year or program cycle. A program plan carries the program name, total credits, and revision date; a course syllabus carries the course name, class hours, and the signature of the author; a credit structure table carries the module name, credit count, and review signature. When these three types of materials enter the form input node, each serves as the counterpart of the fields to be filled: program plan fields correspond to the program and total credits, course syllabus fields correspond to the course and signature, and credit structure table fields correspond to the module and count. Field characteristics are concentrated in four types: name, count, date, and signature. The same record often shows mismatches in name, count, and date across two materials, and cases where versions are not synchronized or signatures and receipts are missing also occur.
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 externally available entry point and authorization scope are then completed by subsequent nodes or manually. After this node is triggered, the conversation enters the interaction state and the workflow state is recorded. After the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Program plan | Whether the program name, total credits, and revision date are consistent across the three materials | Check the field names one by one in the node configuration, reference the field after submission, and run a test |
| Course syllabus | Whether the course name, class hours, and author signature match the program plan | Check the required settings one by one and confirm that key material fields are marked as required |
| Credit structure table | Whether the module name, credit count, and review signature are consistent with the program plan | Reference the field values in subsequent nodes and check whether they can be retrieved after submission |
| Form input node | Whether it can be submitted when required items are empty, and whether the conversation stays in the interaction state | Configure the formInputResult field and run a test, then check the field passing after submission |
Three common errors
- Symptom: the name, count, and date of the same record do not match across two materials. Cause: field names were not checked one by one according to the category's verification dimensions, and material versions were not synchronized.
- Symptom: the credit counts in the program plan and the course syllabus are inconsistent. Cause: the update cadence of revision drafts is not synchronized, and old-version fields are still referenced.
- Symptom: the course syllabus lacks the author's signature or receipt. Cause: the required marking does not cover the signature field, and no signature information can be checked after submission.
How to verify the setup
Acceptance of 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 result.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and confirm that unauthorized content is not visible.
- Check the field names and required settings one by one in the node configuration, and confirm that the program plan, course syllabus, and credit structure table fields correspond one to one.
- Reference the
formInputResultfield in subsequent nodes and run a test to check whether values can be retrieved after submission, whether it can be submitted when required items are empty, and whether the conversation stays in the interaction state.