What this category's data looks like
This category involves three core types of materials: talent cultivation programs, course standards, and job competency analysis tables. Talent cultivation programs come from the academic affairs office and the professional construction committee, revised once per academic year, with fields including program name, program length, cultivation objectives, course modules and credit hours/credits, and signature fields; course standards come from course teams, updated in sync with the program, with fields including course name, objectives, content, credit hours, assessment methods, and approval signatures; job competency analysis tables come from industry-enterprise research, dynamically adjusted by program, with fields including job name, competency items, corresponding courses, research date, and expert signature. When these three types of materials enter the deployment, operations, and application handover stage, the talent cultivation program serves as the master outline determining the version baseline, course standards serve as branch bases corresponding to course modules, and job competency analysis tables serve as the competency mapping source for verifying course coverage. During handover, the materials must maintain consistent names, quantities, and dates, synchronized versions, and complete signatures and receipts.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Handover-ready deployment status and operation records" are then completed by subsequent nodes continuing execution along 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 |
|---|---|---|
| Talent cultivation program | Whether fields, dates, and signatures are consistent with the course standards and job competency analysis table; whether versions are synchronized | Check item by item the program name, program length, course modules, credit hours/credits, signature fields, and signing dates, and compare against the corresponding records in the other two materials |
| Course standards | Whether course names, credit hours, assessment methods, and approval signatures match the talent cultivation program and job competency analysis table | Check options and branch connections one by one in the node, confirm each course corresponds to one branch, and reference variables to check whether the selection result variable is passed |
| Job competency analysis table | Whether job names, competency items, corresponding courses, research dates, and expert signatures are consistent with the other two materials | Trigger a user selection node once, view the node status and nodeId in the run records, and confirm the interaction state is recorded and the branch direction is correct |
| User selection node | Whether options and branches correspond one-to-one; whether the interaction state is recorded; whether the selection result variable is passed to subsequent nodes | Test-run each option, check whether the variables reference takes effect in subsequent nodes, and check whether selecting an option still follows the default branch or the process stalls |
Three common errors
- Symptom: The name and credit hours of the same course do not match between the talent cultivation program and the course standards. Cause: The two materials were revised separately, versions were not synchronized, and fields were not checked item by item during handover.
- Symptom: The research date and expert signature are missing from the job competency analysis table, and the approval field in the course standards is blank. Cause: Receipts are missing in the material circulation step, and signatures and dates were not completed along with version updates.
- Symptom: After selecting an option, the default branch is still followed, and the process stalls after the interaction is completed. Cause: Options and branch connections were not checked one by one, and the selection result variable was not correctly passed to subsequent nodes.
How to verify the setup
Feature acceptance: Test-run each option one by one, check the branch direction and interaction state in the run records, and confirm that the records corresponding to variables and nodeId are complete.
Business testing: Check item by item once according to the handover form, see which record is missing, and compare the fields, dates, and signatures of the talent cultivation program, course standards, and job competency analysis table.
- In the user selection node, check options and branch connections one by one, confirm each option corresponds to one branch, and record the reference relationship between
nodeIdandvariables. - Trigger an interaction once, view the node status and branch direction in the run records, and check the names, quantities, dates, and signatures of the talent cultivation program, course standards, and job competency analysis table according to the handover form.