What this category's data looks like
Vocational school student internship management involves three types of materials: internship agreements, internship plans, and internship logs. The internship agreement contains the names of the three parties, the internship position, start and end dates, signatures, and receipts; the internship plan contains the batch, number of positions, weekly schedule, and supervising teacher's signature; the internship log contains dates, task entries, and mentor signatures. Materials are updated by semester or batch, and the version is determined by the signature date and receipt. When entering the workflow, the agreement serves as the basis draft, the plan serves as the progress baseline, and the log serves as the process evidence, each providing entry sources that can be traced back to the original text, for subsequent nodes to continue execution by branch.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Basis entries that can be traced back to the original text" are completed by subsequent nodes continuing execution by branch. When a 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 |
|---|---|---|
| Internship agreement | Whether the fields, dates, and signatures match the internship plan | Check the options and branch connections one by one in the node, reference variables to record the selected materials, and run a trial to see the branch direction |
| Internship plan | Whether the name, quantity, and dates of the same record are consistent with the log | Reference nodeId and the selection result variable in subsequent nodes and run a trial, and check the node status in the run record |
| Internship log | Whether the version is current, and whether signatures or receipts are missing | Trigger a user selection node once, and check the interaction state and branch direction in the run record |
| User selection node | Whether each option corresponds to one branch and correctly passes the selection result variable | Check the options and branch connections one by one in the node, and reference variables in subsequent nodes for a trial run |
Three common errors
- Symptom: The position name, number of people, and start and end dates of the same internship record do not match between the agreement and the plan. Cause: The two materials were entered separately and field alignment was not performed.
- Symptom: The log still references the weekly schedule of the old plan, and the current version has not been synchronized. Cause: After the materials were updated, they were not re-entered into the workflow to check the branches.
- Symptom: The agreement lacks student or parent signatures, and the log lacks a mentor receipt. Cause: When collecting materials, signatures and receipts were not listed as traceable entries.
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, and check in subsequent nodes the selection result variable passed by variables and nodeId.
Business test: ask a cross-material basis question and see whether the answer provides a traceable source.
- Check the options and branch connections one by one in the node, and trigger once to view the interaction state in the run record.
- Reference the selection result variable in subsequent nodes and run a trial, and check the branch direction and node status.