What this category's data looks like
This category's data looks like this: The formulation of talent cultivation programs in vocational colleges involves three core types of materials: talent cultivation programs, course standards, and job competency analysis tables. The talent cultivation program is drafted under the leadership of the academic affairs office, the course standards are submitted by the teaching and research offices of each major, and the job competency analysis tables are provided by the professional construction committee. The three are updated by academic year and revised in sync when there are major adjustments or policy changes. Material fields include course name, class hours and credits, semester offered, job title, competency requirements, preparer, reviewer, approver, and dates. When the materials enter the workflow orchestration function, the talent cultivation program serves as the master record, while the course standards and job competency analysis tables serve as comparison sources, used to trace whether the names, quantities, dates, and signatures of the same course or job in different materials are consistent. Exception tracing requires locating the original records in reverse from the exception list, while manual review relies on the reviewer's signature for confirmation, and is ultimately handed over to the person in charge for disposition.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "exception list and review conclusions" are then completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interactive 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 |
|---|---|---|
| Talent cultivation program | Course name, class hours and credits, semester offered, preparer, and approver signature and date are self-consistent within the program | Check the program fields and approval signatures item by item; mark an exception when a missing signature or a date inversion is found |
| Course standard | Course name, class hours and credits, and semester offered are consistent with the corresponding records in the talent cultivation program, and the reviewer's signature is complete | Compare the course standard fields with the program one by one; record a discrepancy when the name, quantity, or date does not match |
| Job competency analysis table | The job title and competency requirements correspond to the course objectives in the course standard, and the version number and date are in sync | Check the version dates of the analysis table and the course standard; register an exception when the version is not in sync or the receipt is missing |
| Workflow node | Each option corresponds to one branch, the interaction state is recorded, and the selection result variable has been passed to subsequent nodes | Check the options and branch connections one by one in the node, trigger it once to view the node state in the run record, reference variables in subsequent nodes and do a trial run, and check the branch corresponding to nodeId |
Three common errors
- Symptom: The name and class hours of the same course do not match between the talent cultivation program and the course standard. Cause: The two materials were revised separately, without field-level comparison and version synchronization.
- Symptom: The version of the job competency analysis table is not in sync and still references the old course standard. Cause: After revision, the version number and date were not updated, and receipt confirmation was missing.
- Symptom: The review conclusion lacks the reviewer's signature or receipt. Cause: After the interaction is completed, the process stops and does not continue through the branch, so the signature step is skipped.
How to verify the setup
How to verify the setup: Acceptance of this function: run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and that the variables and nodeId references are correct.
Business test: create an exception record and see whether the source material can be traced, and check the fields, dates, and signatures of the talent cultivation program, course standard, and job competency analysis table.
- Check the options and branch connections one by one in the node, trigger it once to view the node state in the run record, and confirm that the interaction state is recorded.
- Reference
variablesin subsequent nodes and do a trial run once, check the branch direction corresponding tonodeId, and confirm that the selection result variable has been passed.