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 is signed by three parties—the school, the enterprise, and the student—and includes the position, duration, insurance, signatures, and receipt; the internship plan is arranged by the supervising teacher and includes weeks, position rotation, assessment methods, and approval signatures; the internship log is filled in daily by the student and includes date, working hours, tasks, and the enterprise mentor's signature. The three types of materials come from different sources and have different update rhythms: agreements are signed in a concentrated manner before the internship, plans are adjusted by batch, and logs are submitted daily or weekly. When materials enter workflow orchestration, the agreement and plan serve as baseline materials, while the log serves as the material to be verified, respectively assuming the roles of baseline and comparison. Field characteristics are concentrated in four categories: name, quantity, date, and signature. The same record must remain consistent across the three materials, and discrepancy localization is carried out around these four categories of fields.
Configuration and implementation checks
This step is executed by the workflow node (user selection and branching), outputting the branch direction and interaction state record. The "discrepancy list" is then completed by subsequent nodes continuing execution according to the branch. When the user selection 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 the name, quantity, date, signature, and receipt are consistent with the ledger | Compare the position name, internship start and end dates, signature field, and receipt in the agreement one by one, and record the discrepancy fields |
| Internship plan | Whether the weeks, position rotation, assessment method, and approval signature are aligned with the agreement | Check the name, quantity, and date of the plan and agreement by week, and mark versions that are not synchronized |
| Internship log | Whether the date, working hours, tasks, and enterprise mentor's signature correspond to the plan | Compare the log and plan one by one by date, and locate fields where the name, quantity, or date do not match |
| User selection node | Whether the options and branch connections correspond one-to-one, and whether the interaction state is recorded | Check the options and branch connections one by one in the node, reference variables and run a trial once, and view the nodeId and branch direction in the run record |
Three common errors
- Symptom: The dates of the same record do not match between the agreement and the log. Cause: The two materials are updated separately, versions are not synchronized, and the baseline material is not refreshed when adjustments are made.
- Symptom: The same position name is written differently in the plan and the log. Cause: The name is not unified, entries are filled in according to individual habits, and field-level comparison is lacking.
- Symptom: The log lacks the enterprise mentor's signature or receipt. Cause: The signature step is not included in the verification checklist, and the confirmation status is not written back after submission.
How to verify the setup
Acceptance of this feature: Run a trial for each option, check the branch direction and interaction state in the run record, confirm that the options and branch connections are consistent, and check the reference results of variables and nodeId in subsequent nodes.
Business test: Use a real record to find fields inconsistent with the ledger, locate discrepancies in name, quantity, date, or signature, submit them to the reviewer for confirmation, and write back.
- In the user selection node, check the options and branch connections one by one, and after a trial run, view the branch direction and interaction state in the run record.
- In subsequent nodes, reference
variablesandnodeIdto confirm that the selection result has been passed, then continue executing discrepancy localization according to the branch.