What this category's data looks like
Vocational college program filing materials usually consist of three parts: the program filing form, the talent demand justification, and the faculty and equipment list. Their sources are scattered across academic affairs, secondary schools/departments, and human resources and equipment departments, and their update cadence follows the application season and review cycle. The program filing form carries the program name, code, program length, and signature fields; the talent demand justification provides the industry positions, quantities, and date basis; the faculty and equipment list sets out teacher titles, quantities, and equipment values. When the materials enter the workflow, the filing form serves as the main record, while the justification and list serve as supporting attachments, and the fields must be aligned item by item.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Version ledger and change records" is continued and completed by subsequent nodes according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Program filing form | Whether the program name, code, program length, and signature date are consistent with the justification materials | Check the options and branch connections one by one in the node, confirm the branch direction corresponding to the filing form fields, and record the interaction state |
| Talent demand justification | Whether the position names, demand quantities, and justification date match the filing form | Reference variables and nodeId to run a trial once, and check whether the selection result variable obtained by subsequent nodes points to the justification materials |
| Faculty and equipment list | Whether the number of teachers, titles, and equipment values are synchronized with the filing form and justification materials | Check whether the list signatures and receipts are complete, and confirm that the old version is traceable and the current version is unique |
| Version ledger and change records | The current version is unique, the old version is traceable, and references are synchronized | After changing one piece of content, check whether the version number and references are updated synchronously, and record the branch direction |
Three common errors
- Symptom: The program name, quantity, and date of the same record do not match between the filing form and the justification materials. Cause: The two materials are maintained separately, and the fields have not been cross-checked.
- Symptom: After a version of the materials has been changed, the ledger version number is not synchronized, and subsequent nodes still reference the old version. Cause: The version update did not trigger a reference synchronization check.
- Symptom: The filing form or list lacks signatures or receipts, but the process continues downward. Cause: Signature fields and receipts were not included in the branch judgment conditions.
How to verify the setup
Feature acceptance: run trials option by option, check the branch directions and interaction states in the run records, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- Check the options and branch connections one by one in the node, and reference
variablesandnodeIdto run a trial once, confirming that the selection result variable has been passed to subsequent nodes. - Check the names, quantities, dates, and signature receipts of the three materials: the filing form, the justification, and the list, and confirm that the current version is unique and the old version is traceable.