What this category's data looks like
This category's data involves three types of materials: the program setup filing form, the talent demand justification, and the faculty and equipment list. The filing form comes from the institution's application system and contains the program name, code, program length, and enrollment number; the talent demand justification comes from industry research reports and contains the job name, demand quantity, and research date; the faculty and equipment list comes from the school's asset ledger and contains teacher names, titles, equipment names, and quantities. Materials are updated according to the academic-year application cadence, and the fields are mainly names, quantities, dates, signatures, and receipts. When entering this feature, the filing form serves as the primary record, while the talent demand justification and the faculty and equipment list serve as comparison sources; the three are aligned by the same program object for workflow nodes to check item by item.
Configuration and implementation checks
This step is executed by a workflow node (user selection and branching), outputting the branch direction and interaction state records. The "discrepancy list" is completed by subsequent nodes continuing execution according to the branch. When the node is triggered, the conversation enters the interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Program setup filing form | Whether the program name, program code, program length, enrollment number, filing date, signature, and receipt are complete | Compare field by field with the talent demand justification and the faculty and equipment list, check whether the name, quantity, and date are consistent, and mark if the signature or receipt is missing |
| Talent demand justification | Whether the job name, demand quantity, research date, and justification signature correspond to the same program object as the filing form | Align by program object, check whether the job name and demand quantity are consistent with the filing form, and check whether the order of the research date and the filing date is reasonable |
| Faculty and equipment list | Whether the teacher names, titles, equipment names, equipment quantities, list date, and signature correspond to the same program as the filing form | Align by program object, check whether the number of teachers and the number of equipment are consistent with the filing form, and check whether the list date and version are synchronized |
| User selection node | Whether the options and branches correspond one to one, and whether the selection result variable is passed to subsequent nodes | Check the options and branch connections one by one in the node, trigger it once to view the node status in the run record, and reference variables in subsequent nodes and do a trial run |
Three common errors
- Symptom: the name or quantity of the same program does not match across two materials. Cause: the materials are filled in independently, are not aligned by the same object, and the fields are not cross-checked.
- Symptom: the date or version of the filing form and the faculty and equipment list are not synchronized. Cause: after the list is updated, it is not written back to the filing form, and the version number and date are not adjusted with the change.
- Symptom: the filing form lacks a signature or receipt, and the process stops after the interaction is completed. Cause: the materials are not fully collected before entering the node, and the branch direction and interaction state are not recorded according to the selection result.
How to verify the setup
For this feature's acceptance: run a trial for each option one by one, check the branch direction and interaction state in the run record, and check the node status corresponding to nodeId and the variables passing result.
Business test: use one real record to find fields inconsistent with the ledger, and check the name, quantity, date, signature, and receipt.
- In the user selection node, check the options and branch connections one by one, and confirm that each option corresponds to one branch.
- Trigger the node once, view the node status and selection result variable in the run record, and confirm that they have been passed to subsequent nodes.