What this category's data looks like
This category's data looks like this: The filing of program setup in vocational colleges involves three core types of materials: the program setup filing form, the talent demand justification, and the faculty and equipment list. The filing form contains the program name, code, program length, enrollment scale, and the signature and date of the person in charge; the talent demand justification contains the survey subjects, job correspondence, data sources, and justification conclusion; the faculty and equipment list contains teacher names, titles, quantities, equipment names, specifications, and quantities. The materials come from the academic affairs office, secondary colleges, and the human resources department, and are updated by academic year or application batch, with cross-table reference relationships among fields. When entering the workflow, the filing form serves as the main record, while the justification and list serve as supporting attachments; together, the three constitute the source of fields for a draft that can be issued, and any missing field or cross-table inconsistency will affect subsequent receipt.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The issuable material draft and handover record are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an 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, code, program length, enrollment scale, and the signature and date of the person in charge are complete and consistent with the justification and list | Check the options and branch connections one by one in the node, use nodeId to locate the node, and after a trial run check the node status in the run record |
| Talent demand justification | Whether the survey subjects, job correspondence, data sources, justification conclusion, and date are complete, and whether the name and quantity in the same record match the filing form | Reference the selection result variable in variables in a subsequent node and run a trial once, then check the fields of this material against the filing form |
| Faculty and equipment list | Whether teacher names, titles, quantities, equipment names, specifications, and quantities are complete, and whether signatures or receipts are attached | Trigger a user selection node once, check the node status and branch direction in the run record, and check the quantities in the list against the filing form |
| Handover record | Whether the responsible person, version, date, and receipt are clear, and whether the receipt destination is consistent with the branch direction | Draft one according to the template and complete one handover, check whether missing items are blocked, and check the handover record against the branch direction |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the filing form and the faculty and equipment list. Cause: Cross-table reference fields are not synchronized, and each is filled in separately during drafting.
- Phenomenon: The version is not synchronized, and the handover record references an old version of the filing form. Cause: The version field is not updated with the branch, and subsequent nodes still read the old variable.
- Phenomenon: A signature or receipt is missing, and the material cannot be issued. Cause: The responsible person field is not filled in, and the handover step does not trigger receipt confirmation.
How to verify the setup
How to verify the setup: Acceptance of this function: run trials for each option one by one, check the branch direction and interaction state in the run record, and confirm that variables and nodeId can be referenced in subsequent nodes.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the node, trigger a user selection once, and check the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once, then check the fields, dates, and signatures of the filing form, justification, and list.