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 organization name, position, start and end dates, and signature fields for the student and the organization; the internship plan contains the weekly schedule, task items, supervising instructor, and dates; the internship log contains daily records, work hours, mentor signatures, and receipts. The materials come from academic affairs, secondary colleges, and internship organizations, are updated by semester, and versions change with position adjustments and supplementary signatures. When entering this feature, the agreement and plan serve as terminology sources and comparison benchmarks, while the log serves as the object for item-by-item comparison; together, the three types of materials support the generation of a unified terminology glossary and a comparison draft. Terminology translations must be able to refer back to the source text, and the same term must be written consistently throughout.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "unified terminology glossary and comparison draft" is then completed by subsequent nodes continuing execution according to the branch. When a node is triggered, the conversation enters an interactive state and records the workflow state; after the selection is completed, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | Whether the fields, dates, and signatures are consistent with the plan and log | Check the organization name, position, start and end dates, and signature fields one by one, verify the options and branch connections one by one in the node, and use variables to reference the selection result for a trial run |
| Internship plan | Whether the weekly schedule and task items correspond item by item with the log | Extract task items by week, check the name, quantity, and date of the same record in both materials, and check whether the versions are synchronized |
| Internship log | Whether the daily records, work hours, and mentor signature receipts are complete | Spot-check log entries against the agreement and plan, review the node status in the run records, and confirm that nodeId corresponds to the branch direction |
| Unified terminology glossary and comparison draft | Whether the same term is written consistently throughout and whether the translation can refer back to the source text | Spot-check three terms for their writing throughout, verify the refer-back relationship between the comparison draft and the source text, and confirm that subsequent nodes continue execution according to the branch |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the agreement and the plan. Cause: The two materials are maintained separately, and no field-level comparison was performed before entering the workflow.
- Phenomenon: The log version and plan version are not synchronized, and tasks from an old week are still referenced. Cause: The update rhythms differ, and there is no version synchronization check step.
- Phenomenon: The agreement lacks a signature or the log lacks a receipt, yet the terminology glossary is still generated. Cause: Material completeness was not determined before branch selection, and signature and receipt checks were omitted.
How to verify the setup
This feature acceptance: Run trials option by option, check the branch directions and interaction states in the run records, confirm that the options and branch connections are consistent, and reference the selection result variable in a subsequent node for one trial run.
Business test: Spot-check three terms for consistent writing throughout, verify whether the translations can refer back to the source text, and confirm that the comparison draft corresponds item by item with the unified terminology glossary.
- In the node, verify the options and branch connections one by one, confirm that each option corresponds to one branch, and record the interaction state.
- Reference the selection result variable in a subsequent node and run a trial, checking the branch directions and interaction state records corresponding to
variablesandnodeId.