What this category's data looks like
This page addresses vocational school student internship management materials, with the core categories being internship agreements, internship plans, and internship logs. Internship agreements state the internship unit, position, duration, rights and responsibilities of both parties, and signatures and seals; internship plans state the batch, cycle, rotation arrangements, and supervising teacher confirmation; internship logs record the position, tasks, duration, and mentor signature on a daily or weekly basis. The material sources are submissions from three parties: the school's academic affairs and internship management department, the internship unit's mentor side, and the student. The update rhythm is that agreements are occasionally changed after one-time signing, plans are fine-tuned after being issued by batch, and logs are continuously added on a daily or weekly basis. When materials enter workflow orchestration, agreements and plans serve as the basis for authorization scope, and logs serve as filtering materials for visible scope; together, the three determine which entry points and fields are opened to parents or superiors. Field characteristics center on dates, quantities, names, signatures, and receipts, and the same record must maintain consistent names, quantities, and dates across the three materials.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Externally available entry points and authorization scope" are then completed by subsequent nodes continuing execution according to the branch. When a 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 |
|---|---|---|
| Internship agreement | Whether names, quantities, dates, and signatures and seals are consistent across the three materials, and whether versions are synchronized | Compare the unit name, position name, and internship start and end dates in the agreement against the plan and logs one by one, and check whether signatures and receipts are complete |
| Internship plan | Whether the batch, cycle, rotation arrangements, and supervising teacher confirmation are consistent with the agreement, and whether versions are synchronized | Check the plan dates against the agreement duration by batch, and check the supervising teacher's confirmation signature in the plan and logs |
| Internship log | Whether the position, tasks, duration, and mentor signature match the plan and agreement | Spot-check log entries on a daily or weekly basis, comparing position name, task quantity, dates, and mentor signature |
| User selection node | Whether each option corresponds to one branch, and whether the selection result variable is passed to subsequent nodes | In the node, check the options and branch connections one by one, trigger once and view the node status in the run record, reference variables in subsequent nodes and run a test, and check the branch corresponding to nodeId |
Three common errors
- Phenomenon: The position name, quantity, and date of the same internship record do not match between the agreement and the log. Cause: The two materials are entered separately, lacking cross-comparison and version synchronization.
- Phenomenon: The internship plan has been updated, but the log and agreement are still executed according to the old version. Cause: Versions are not synchronized, and changes are not receipted to each material.
- Phenomenon: The internship log lacks a mentor signature or receipt, but the external entry point is still visible. Cause: Signatures and receipts are not included in the visible scope determination.
How to verify the setup
This feature acceptance: test each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to a branch, that the selection result variable has been passed to subsequent nodes, and that the variables and nodeId references are correct.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and confirm that unauthorized content is not visible.
- In the user selection node, check the options and branch connections one by one, trigger once, and view the node status and branch direction in the run record.
- Reference
variablesin subsequent nodes and run a test once, checking whether the branch corresponding tonodeIdis consistent with the interaction state record.