What this category's data looks like
Vocational college program setup filing materials come from filing forms, talent demand justification, and faculty and equipment lists submitted by the academic affairs and program development departments of institutions by academic year or application cycle. The update cadence follows application batches and internal review milestones, and the field characteristics center on names, quantities, dates, signatures, and receipts. The filing form plays the master record role, recording the program name, code, program length, and application date; the talent demand justification plays the basis role, providing descriptions of industry positions and regional demand; the faculty and equipment list plays the conditions role, listing the number of teachers, the title structure, and the number of training equipment units. After the three types of materials enter the workflow, the user first selects a node to trigger the interaction state, then flow proceeds along option branches, and subsequent nodes respectively take on progress recording and statistical verification, forming a progress table and a statistical scope note.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "progress table and statistical scope note" is completed next by subsequent nodes continuing execution along the branches. When a 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 fields, dates, and signatures correspond to the talent demand justification and faculty and equipment list | Compare program names, codes, quantities, and dates one by one, verify whether signatures and receipts are complete, and check the options and branch connections in the node |
| Talent demand justification | Whether the names, quantities, and dates of the same record match across the two materials | Extract position names and demand quantities, compare them item by item with the filing form, check whether versions are synchronized, and reference variables to confirm that the selection result variable has been passed in |
| Faculty and equipment list | Whether the number of teachers, title structure, and equipment units are consistent with the filing form | Check the list totals against the filing form's line items, inspect entries missing signatures or receipts, and use nodeId to locate the corresponding node run record |
| Progress records and statistical verification | Whether the record count matches the statistical count and the scope is written in the header | Summarize the number of records by week, check totals against exception notes, and confirm that branch directions are consistent with the interaction state records |
Three common errors
- Symptom: The names, quantities, and dates of the same program do not match across the two materials. Cause: The scope was not unified during entry, field sources were not synchronized, and verification compared only totals rather than details.
- Symptom: The filing form has been updated, but the justification and list are still the old version. Cause: Versions were not synchronized, changes were not sent back, and node branches continued executing according to the old records.
- Symptom: The list is missing signatures or receipts, but the progress table still shows everything as collected. Cause: Receipt and verification are separated, signature status is not written into the records, and unsigned entries are included in the total during statistics.
How to verify the setup
Feature acceptance: trial-run each option, check the branch directions and interaction states in the run records, confirm that options and branches correspond one to one, that the selection result variable has been passed to subsequent nodes, and locate them by referencing variables and nodeId.
Business testing: use one week of records to verify the totals, check whether the scope and exceptions are clearly written, and whether the record count matches the statistical count.
- Check the options and branch connections one by one in the node, trigger it once, and view the node status in the run records.
- Reference the selection result variable in a subsequent node and trial-run it once to confirm that the process continues downward after the interaction is completed.