What this category's data looks like
Vocational college program filing materials usually consist of three sources: the program filing form, the talent demand justification, and the faculty and equipment list. The filing form is updated according to the academic-year application cycle, and its fields include program name, code, program length, enrollment scale, signature, and date; the talent demand justification comes from industry research, and its fields include job title, demand quantity, research date, and justification conclusion; the faculty and equipment list is checked per semester, and its fields include teacher name, professional title, equipment name, quantity, and purchase date. When the three materials enter the workflow, their roles differ: the filing form is the main record, the talent demand justification is used to support missing-item follow-up questions, and the faculty and equipment list is used for cross-comparison. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures. It is common for the same record to have inconsistent names across two materials, mismatched quantities, misaligned dates, or unsynchronized versions, missing signatures, and missing receipts.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Acceptance records and items to be completed" are continued and completed by subsequent nodes according to the branches. 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 filing form | Whether fields, dates, and signatures are complete, and whether the program name and code are consistent with the justification materials | In the node, check the options and branch connections one by one, trigger once to view the node status in the run record, and reference variables to record the selection result |
| Talent demand justification | Whether the job title, demand quantity, and research date correspond to the filing form, and whether the justification conclusion has a signature | In a subsequent node, reference this variable and run a trial once, and check whether the branch corresponding to nodeId proceeds to follow-up questions according to the selection result |
| Faculty and equipment list | Whether teacher name, professional title, equipment name, quantity, and purchase date are consistent with the filing form | In the node, check the options and branch connections one by one, and check whether variables have been passed to subsequent nodes |
| Acceptance records and items to be completed | Whether missing items are identified and followed up on, and whether answers are supported by materials | Trigger once, view the node status in the run record, and confirm the branch direction and interaction state record |
Three common errors
- Phenomenon: The name and quantity of the same record do not match between the filing form and the faculty and equipment list. Cause: The two materials are updated separately, and acceptance proceeds without cross-comparison.
- Phenomenon: The version of the talent demand justification is not synchronized, and the research date is misaligned with the filing form date. Cause: After the justification material is updated, it is not written back to the main record, and the node still follows the branch according to the old version.
- Phenomenon: The filing form lacks a signature or receipt, and after follow-up it is still directly forwarded to the handler. Cause: Missing-item identification does not reach the field level, and the branch direction is not re-judged according to the completion result.
How to verify the setup
Acceptance of this function: run trials option by option, check the branch direction and interaction state in the run record, and confirm the correspondence between variables and nodeId.
Business test: submit a question that lacks key information and see whether it asks a follow-up question before answering.
- In the node, check the options and branch connections one by one, and trigger once to view the node status in the run record.
- In a subsequent node, reference the selection result variable and run a trial once, and check the branch direction and interaction state record.