What this category's data looks like
This page addresses the scenario of vocational school student internship management. The core materials include three types: internship agreements, internship plans, and internship logs. The internship agreement is signed by three parties: the school, the internship organization, and the student. Its fields include the names of the three parties, internship position, start and end dates, responsibility clauses, and signature fields. The internship plan is jointly drafted by the professional teacher and the internship organization. Its fields include internship objectives, rotation arrangements, supervisor, assessment methods, and approval signature. The internship log is filled in by the student daily or weekly. Its fields include date, position, task content, supervisor confirmation, and receipt. The three types of materials have different sources and different update rhythms: agreements are mostly signed once before the internship, plans are revised as rotations are adjusted, and logs are continuously added on a periodic basis. When entering workflow orchestration, the agreement serves the role of responsibility handover basis, the plan serves the role of node branch condition, and the log serves the role of process record and receipt evidence. The fields, dates, and signatures of the three must remain consistent on the same record.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The material drafts and handover records that can be issued are 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 status. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | Whether the names of the three parties, internship position, start and end dates, responsibility clauses, and signature fields are complete, and whether dates and signatures are consistent | Check the options and branch connections one by one in the node, confirm that the agreement fields are complete, and then proceed to the next step for receipt |
| Internship plan | Whether internship objectives, rotation arrangements, supervisor, assessment methods, and approval signature are complete, and whether version and date are synchronized | Reference the selection result variable in subsequent nodes and run a trial once, checking whether the plan version corresponds to the agreement date |
| Internship log | Whether date, position, task content, supervisor confirmation, and receipt are complete, and whether the name and quantity in the same record are consistent with the agreement and plan | Trigger an interaction state once, view the node status in the run record, and check whether the log receipt has missing items |
| Handover record | Whether the responsible person, handover date, receipt status, and version number are clear, and whether the receipt is retained | Check the handover record fields and branch direction, and after confirming that missing items are blocked, it may be handed to the next step for receipt |
Three common errors
- Phenomenon: The position name and date of the same internship record do not match between the agreement and the log. Cause: The two materials were drafted separately, and the fields and dates were not checked in the same node.
- Phenomenon: After the internship plan is revised, the version is not synchronized to the agreement and log. Cause: The version number and date were not passed along with the branch direction, and subsequent nodes still reference the old version.
- Phenomenon: The handover record lacks a signature or receipt, but the process still continues downward. Cause: The node did not block missing items, and the interaction state and selection result variable were not validated by subsequent nodes.
How to verify the setup
Acceptance of this feature: Run trials option by option, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, and that the selection result variable has been passed to subsequent nodes. Reference variables and nodeId for checking.
Business test: Draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and check whether the
nodeIdandvariablesreferences are correct. - Trigger an interaction state once, view the node status in the run record, and confirm that the process continues after the interaction is completed and that the selection result variable has been passed to subsequent nodes.