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 sources are school academic affairs, internship units, and supervising teachers, and the update cadence changes with internship batches, position adjustments, and agreement renewals. Internship agreements include unit name, position, start and end dates, and signatures and seals; internship plans include batch, week number, tasks, and signatures; internship logs include date, position, work content, quantity, and signed receipt. When materials enter workflow orchestration, the agreement serves as the baseline version, the plan serves as the batch version, and the log serves as the process record version. Each plays its own role in version comparison and reference synchronization. The user selection node triggers the branch direction, and subsequent nodes continue execution according to the branch.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive 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 fields, dates, and signatures are consistent with the current version | Check the options and branch connections one by one in the node, and see whether the agreement name, quantity, date, and signature are synchronized with the plan and log |
| Internship plan | Whether the name, quantity, and date of the same record match across the two materials | Trigger a user selection once, and check the node status and branch direction in the run record |
| Internship log | Whether the correction branch is taken when the signature or receipt is missing | Reference the selection result variable in a subsequent node and run a trial once, and check whether the variable has been passed to the subsequent node |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | Change one piece of content, see whether the version number and references are updated synchronously, and record the number of array entries and the tokens of the reference text |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the agreement and the plan. Cause: The version is not synchronized, and the reference still points to the old version content.
- Symptom: An internship log missing a signature or receipt still enters the subsequent process. Cause: The branch judgment does not cover the correction option, and the interaction status record is incomplete.
- Symptom: After selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed to the subsequent node.
How to verify the setup
Feature acceptance: Run trials for each option one by one, check the branch direction and interaction status in the run record, confirm that options and branches correspond one to one, and that nodeId and variables are queryable in the run record.
Business test: Change one piece of content, see whether the version number and references are updated synchronously, and record the number of references and the tokens of the reference text.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference
variablesin a subsequent node and run a trial once, check whether the selection result variable has been passed to the subsequent node, and record the node status corresponding tonodeId.