What this category's data looks like
This page focuses on exception tracing and manual review in vocational school student internship management. The source materials are three types of original records: internship agreements, internship plans, and internship logs, updated by batch or semester. Fields cover student name, internship organization name, position, start and end dates, number of check-ins, mentor signature, and organization receipt. When the exception list and review conclusions enter this function, the agreement serves as the comparison baseline for the agreed entity and term, the plan serves as the comparison baseline for position and time arrangement, and the log serves as the comparison baseline for daily records and signatures; the names, quantities, dates, and signatures of the three must corroborate one another, and any mismatch triggers tracing.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The "exception list and review conclusions" are parsed by subsequent nodes from the response, or handled and completed by an external system according to the agreement.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | The entity name, internship start and end dates, signature, and receipt must be consistent with the plan and log | Compare the organization name and dates of the same student across the three materials; if the signature or receipt is missing, mark it as an exception |
| Internship plan | The position, batch, and time arrangement must correspond to the agreement terms and log records | Check the positions and dates in the plan one by one; when a version is not synchronized, the latest receipt version prevails |
| Internship log | The quantity, dates, and mentor signature of daily records must be traceable to the source materials | Extract one log record, trace it back to its corresponding agreement and plan entries, and check whether the quantity and dates match |
| HTTP node | The placeholder variables in the request URL, request headers, and request body can be resolved into actual values | View the fully rendered URL in the request preview, and check the value sources of Authorization and variables |
Three common errors
- Symptom: the internship organization name for the same student is inconsistent between the agreement and the log. Cause: the two materials are entered in different steps and are not written back under a unified name.
- Symptom: the number of positions in the plan does not match the daily records in the log. Cause: after the plan version is updated, it is not synchronized to the log side, so the version is not synchronized.
- Symptom: the log lacks a mentor signature or organization receipt. Cause: the signature field is not validated during material collection, so exception records lack original support.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample to confirm that the exception list fields in responseData are consistent with the original records.
Business test: create one exception record and see whether it can be traced back to the source materials
- In the variables panel, check the source of each placeholder and confirm that the variables in path parameters, request body, and request headers can all be traced to global variables, system variables, or outputs of preceding nodes
- Use one sample request to compare the returned fields, and check whether the inputs of
Authorizationandvariablesconform to the external system agreement