What this category's data looks like
Vocational college program setup filing materials mainly consist of three types: program setup filing forms, talent demand justification, and faculty and equipment lists. The sources are institutional applications and competent department archiving, updated by academic year or application batch. The filing form contains the program name, code, program length, and signature fields; the justification materials include industry research data, job correspondence relationships, and dates; the faculty and equipment list sets out the number of teachers, title structure, number of equipment sets, and receipts. When the three types of materials enter workflow orchestration, their roles differ: the filing form serves as the main record anchor, while the justification materials and faculty and equipment list serve as supporting evidence and comparison sources. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures. During cross-material comparison, inconsistencies in how the same record is expressed, unsynchronized versions, and missing signatures or receipts easily occur, so original records must be retained as support for exception tracing and manual review.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The "exception list and review conclusions" are completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interaction 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 |
|---|---|---|
| User selection node | Each option corresponds to one branch, and options and branch connections correspond one by one | In the node, check the options and branch connections one by one, and confirm that the number of options matches the number of branches |
| Interaction status | The status is recorded when entering the node, and one trigger can be viewed in the run record | Trigger the user selection node once, and view the node status and interaction status in the run record |
| Selection result variable | It has been passed to subsequent nodes, and subsequent nodes can reference this variable | Reference variables in a subsequent node and run a trial once, and check the branch direction of the node corresponding to nodeId |
| Program setup filing form and talent demand justification | The name, quantity, and date of the same record do not match in the two materials | Compare the program name, quantity, and date field by field, mark inconsistent items, and retain the original records as support |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match in the filing form and justification materials. Cause: The two materials are filled in separately, without cross-material field comparison and version synchronization.
- Phenomenon: The version of the faculty and equipment list is not synchronized, and old-version quantities coexist with new-version quantities. Cause: Inconsistent update rhythms and lack of version identifiers and receipt verification.
- Phenomenon: The filing form or justification materials lack signatures or receipts. Cause: The archiving step does not verify signature fields and receipts, and exception records cannot be traced back to the source materials.
How to verify the setup
This feature acceptance: run trials option by option, check the branch direction and interaction status in the run record, and confirm that the node corresponding to nodeId is consistent with the variables passing result.
Business test: create an exception record, see whether it can be traced back to the source materials, and check whether the name, quantity, date, and signature are consistent with the original records.
- Run trials on the user selection node option by option, and check the branch direction and interaction status records
- Reference
variablesin a subsequent node and run a trial, and check the selection result of the node corresponding tonodeId