What this category's data looks like
This page focuses on progress records and statistical verification in vocational school student internship management. The source materials are internship agreements, internship plans, internship logs, and weekly/monthly report drafts, with an update cadence of weekly aggregation and monthly verification. Internship agreements provide position, term, and signature fields; internship plans give batches, start and end dates, and supervising instructors; internship logs record attendance, tasks, and signature receipts day by day. When the three types of materials enter the workflow, their roles differ: agreements and plans serve as the baseline headers for statistical scope, logs serve as the source of record counts, and weekly/monthly reports serve as the destination for totals. Field characteristics center on dates, names, quantities, signatures, and version numbers, and the same record often needs to be compared across materials.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "Progress Table and Statistical Scope Description" is continued and completed by subsequent nodes 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 fields, dates, and signatures are consistent with the plan and logs | Verify the position name, start and end dates, signature, and receipt in the agreement, and compare the same-named fields in the plan and logs; check the options and branch connections one by one in the node, and confirm the branch direction records |
| Internship plan | Whether batches, start and end dates, and supervising instructors correspond week by week with the logs | Extract the batches and dates from the plan by week and compare them item by item with the log record counts; reference the selection result variable variables in subsequent nodes and run a trial once |
| Internship log | Whether the names, quantities, dates, and signatures recorded day by day can be aggregated | Use one week of logs to verify the totals, and check whether the scope and exceptions are clearly written; view the node status and nodeId in the run records to confirm that the interaction state is recorded |
| Progress table and statistical scope description | Whether record counts and statistical counts match, and whether the scope is written in the header | Write the statistical scope and exceptions in the header, and verify the record counts and statistical counts; confirm whether the branch direction is consistent when the same session enters the interaction repeatedly |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the agreement and the log. Cause: The two materials are maintained separately and are not compared item by item according to unified fields and date scope.
- Symptom: The plan version is not synchronized, and the weekly report is still aggregated according to the old batch. Cause: The version number is not updated with the materials, and subsequent nodes continue execution by referencing the old variable.
- Symptom: The log lacks a signature or receipt but is still included in the totals during statistics. Cause: The signature field is not verified after the interaction is completed, and exceptions are not written in the header.
How to verify the setup
This feature's acceptance: run trials option by option, verify the branch directions and interaction states in the run records, confirm that the selection result variable variables has been passed to subsequent nodes, and record the node status corresponding to nodeId.
Business test: use one week of records to verify the totals and see whether the scope and exceptions are clearly written; confirm that the record counts and statistical counts match and that the scope is written in the header.
- Check the options and branch connections one by one in the node, and trigger once to view the node status in the run records.
- Reference the selection result variable
variablesin subsequent nodes and run a trial once to confirm that the branch direction is consistent with the interaction state record.