What this category's data looks like
Vocational college program setup filing materials commonly include program setup filing forms, talent demand justification, and faculty and equipment lists. Fields cover program name, code, program length, enrollment number, number of teachers, equipment value, justification date, and signature. Sources are mostly academic affairs offices, secondary colleges, and partner enterprises, and the update rhythm rolls forward according to application batches and correction notices. It often occurs that the same record has inconsistent names, quantities, or dates across two materials, versions are not synchronized, and signatures or receipts are missing. When entering this feature, the filing form serves as the primary record, while the justification and lists serve as comparison sources. Terms and translated names must be able to refer back to the original text, so that subsequent nodes can unify the terminology list and comparison draft.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Unify the terminology list and comparison draft" is continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status. 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 fields, dates, and signatures are consistent with the justification and lists | Check options and branch connections one by one in the node, and after a trial run check the node status and nodeId in the run records |
| Talent demand justification | Whether the same program name, quantity, and date can refer back to the original text | Reference the selection result variables in subsequent nodes and run a trial once, checking whether the justification fields match the filing form |
| Faculty and equipment list | Whether the number of teachers, equipment value, dates, and signatures are complete | Trigger a user selection node once, view the interaction status record, and check whether the list fields are consistent with the filing form |
| Unified terminology list and comparison draft | Whether the same term is written consistently throughout and whether translated names can refer back to the original text | Sample three terms to check whether their writing is consistent throughout, and check the field correspondence between the comparison draft and the filing form, justification, and lists |
Three common errors
- Phenomenon: The program name, enrollment number, and date of the same record do not match between the filing form and the justification. Cause: The two materials are maintained by different departments, and no field-level comparison has been made.
- Phenomenon: The list version is not synchronized, and after correction the old version's number of teachers and equipment value are still referenced. Cause: The version was not updated together with the filing form, and there is a lack of a unified version marker and receipt.
- Phenomenon: The filing form lacks a signature or receipt, and the process stops after the interaction is completed. Cause: Signatures and receipts were not included in node checks, and the branch direction was not fully recorded.
How to verify the setup
Feature acceptance: Run trials for each option one by one, check the branch directions and interaction status in the run records, confirm that each option corresponds to one branch, and that the selection result variables has been passed to subsequent nodes.
Business testing: Sample three terms to check whether their writing is consistent throughout, check whether translated names can refer back to the original text, and check whether the fields, dates, and signatures of the filing form, justification, and lists match.
- Check options and branch connections one by one in the node, trigger a user selection node once, and view the node status and
nodeIdin the run records. - Reference the selection result
variablesin subsequent nodes and run a trial once, sample three terms to check whether their writing is consistent throughout, and check the field correspondence between the comparison draft and the filing materials.