What this category's data looks like
The development of talent cultivation programs in vocational colleges involves three types of materials: talent cultivation programs, course standards, and job competency analysis forms. Talent cultivation programs are usually revised by academic year or program cycle, with fields including program name, cultivation objectives, course structure, credit hours and credits, signatures, and dates; course standards are updated by course, with fields including course name, objectives, content, assessment methods, and signatures of the author and reviewer; job competency analysis forms come from enterprise research, with fields including job name, competency items, corresponding courses, research date, and receipt. When the three types of materials enter workflow orchestration, their roles differ: the talent cultivation program serves as the main document that triggers version branches, while course standards and job competency analysis forms serve as referenced documents that synchronize with the main document. In terms of update rhythm, program revisions drive the linkage of course standards and competency forms, requiring that the current version remain unique, old versions remain traceable, and references stay synchronized.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. When 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. The "version ledger and change records" are completed by subsequent nodes continuing execution along the branch.
| 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 options and branch connections one by one, and view the branch directions and interaction status in the run records |
| Talent cultivation program | Program name, cultivation objectives, credit hours and credits, signatures, and dates are consistent across the program, course standards, and competency forms | Extract records for the same program and compare the names, quantities, dates, and signature receipts of the three materials |
| Course standard | Course name, objectives, and assessment methods are consistent with the corresponding job competency items, and the signatures of the author and reviewer are complete | Check the correspondence between course standards and competency forms one by one by course, and inspect signatures and receipts |
| Job competency analysis form | Job name, competency items, corresponding courses, and research date are traceable, and the receipt is complete | Compare the job and course fields of the competency form with the program and course standards, and check the research date and receipt |
Three common errors
- Phenomenon: For the same record, the course names and credit hour quantities in the program and course standards do not match. Cause: Referenced documents were not updated in sync with the main document, and the field source is not unique.
- Phenomenon: Old versions of materials are still referenced, and the current version is not unique. Cause: The version number was not incremented with content changes, and reference relationships were not synchronized.
- Phenomenon: Course standards lack the author's signature or job competency analysis forms lack a receipt. Cause: The material circulation step did not record signature and receipt status.
How to verify the setup
This feature acceptance: test each option one by one, and check the branch directions and interaction status in the run records; reference the selection result variable variables in subsequent nodes, and check the node status corresponding to nodeId.
Business test: change one piece of content and see whether the version number and references are updated in sync.
- In the user selection node, check options and branch connections one by one, confirming that each option corresponds to one branch.
- Trigger one interaction, view the node status and branch directions in the run records, and confirm that the selection result variable has been passed to subsequent nodes.