What this category's data looks like
Vocational school student internship management materials include internship agreements, internship plans, and internship logs. They originate from three-party circulation among the school's academic affairs and internship management department, the internship unit, and the supervising instructor, and their update rhythm rolls forward with internship batches and monthly log submissions. Agreements contain the unit name, position, start and end dates, and signatures and seals; plans contain the batch, week number, tasks, and supervising instructor; logs contain the date, position, tasks, and signature receipt. When the materials enter the question acceptance and missing-item follow-up function, the agreement and plan serve as the basis for qualification and arrangement, and the log serves as the basis for process records. The fields of the three must corroborate one another in name, quantity, date, and signature, and any missing item triggers a follow-up question.
Configuration and implementation checks
This link is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. "Acceptance records and the items to be completed" are continued and completed by subsequent nodes 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 | Check whether the unit name, position, start and end dates, and signatures and seals are complete, and whether they are consistent with the unit and batch in the internship plan | Check the options and branch connections one by one within the node, reference variables to view the agreement fields, and trigger once to view the node state in the run records |
| Internship plan | Check whether the batch, week number, tasks, and supervising instructor match the agreement's start and end dates, and whether the version is synchronized | Reference the selection result variables in a subsequent node and run a trial once, and compare the date fields of the plan and the agreement |
| Internship log | Check whether the date, position, tasks, and signature receipt are complete, and whether they are consistent with the number of weeks in the plan | Check the options and branch connections within the node, use nodeId to locate the log node, and trigger once to view the interaction state |
| Acceptance records and the items to be completed | Whether missing items are identified and followed up on, and whether the answers have a material basis | Reference variables in a subsequent node and run a trial once, and view the branch direction and interaction state records |
Three common errors
- Phenomenon: The unit name and number of positions for the same record do not match between the agreement and the plan. Cause: The two materials were entered separately and no field comparison was performed, so missing items entered the answering stage without being identified.
- Phenomenon: The log does not match the plan in the number of weeks or dates. Cause: The version was not synchronized, the old plan was still referenced, and the node continued execution along the default branch.
- Phenomenon: The agreement lacks a signature or receipt, and the log lacks a signature. Cause: The signature fields were not verified when the materials were uploaded, and after the interaction was completed the process stalled or took the wrong branch.
How to verify the setup
This function's acceptance: run trials option by option, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, and reference variables and nodeId to locate the node state.
Business test: submit a question that lacks key information, see whether it first asks a follow-up question before answering, and after missing items are identified and followed up on and the answer has a material basis, transfer it to the responsible person for handling.
- Check the options and branch connections one by one in the node, trigger once to view the node state in the run records, and confirm that the selection result variable has been passed to subsequent nodes.
- Reference the selection result variable in a subsequent node and run a trial once, and compare the names, quantities, dates, and signature receipts of the internship agreement, internship plan, and internship log.