What this category's data looks like
Vocational school student internship management materials include internship agreements, internship plans, and internship logs. They come from three parties: academic affairs, internship supervisors, and enterprise mentors, and their update cadence advances with internship batches and monthly milestones. Internship agreements state the position, term, responsibilities, and signatures; internship plans state rotation arrangements, dates, and mentors; internship logs record the position, tasks, duration, and acknowledgments by day or week. When materials enter the HTTP interface and external systems, the agreement serves as the authorization basis determining the visible scope, the plan serves as the scheduling basis determining time fields, and the log serves as the process basis determining detail fields. The three types of materials must align item by item on names, quantities, dates, and signatures. If the fields of the same record do not match across two materials, it is deemed inconsistent. If versions are not synchronized or signatures or acknowledgments are missing, it must not be used as a basis for external services.
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 externally available entry point and authorization scope are parsed from the response by subsequent nodes, or handled by the external system according to the agreement to complete the next step. The HTTP node does not replace the external system in writing to the database or approving; it only delivers the request and retrieves the result.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | The student name, position name, start and end dates, and signature in the agreement must be consistent with the internship plan. Missing signature or acknowledgment is deemed not externally available. | In the request preview, view the complete rendered address, check whether the path parameters and request body fields are taken from the agreement, and compare the response with one sample. |
| Internship plan | The rotation department, mentor, dates, and quantities in the plan must align item by item with the internship log. If versions are not synchronized, it must not be used as an authorization basis. | Check the request header names and value sources, confirm that Authorization is passed in according to the external system's requirements, and then check the source of each placeholder in the variables panel. |
| Internship log | The dates, task names, durations, and acknowledgments in the log must match the agreement and plan. If the same record does not match across two materials, it is judged inconsistent. | Use one sample request to compare the response, check whether the fields in responseData are consistent with the log agreement, and record the source of variables. |
| Authorization scope | The visitor's identity matches the visible scope; unauthorized content is not visible; parents or superiors see only the agreed fields. | Access once with a restricted identity, see whether the visible scope matches the setting, and check the status code and returned fields. |
Three common errors
- Symptom: The request returns 401. Cause: Authentication information was not passed in the request header according to the external system's requirements, or the agreement signature is missing, making the authorization basis incomplete.
- Symptom: The external system receives empty fields. Cause: Variable placeholders were not resolved into actual values, or the internship plan and log versions are not synchronized and the dates do not match.
- Symptom: The request times out. Cause: The target address is unreachable or the path parameter value is incorrect, and the names and quantities of the same record are inconsistent across two materials.
How to verify the setup
Acceptance for this feature: preview the rendered request, check the status code and returned fields, then compare the result against one sample; confirm that the three references Authorization, variables, and responseData are traceable.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, unauthorized content is not visible, and parents or superiors see only the agreed fields.
- In the request preview, check the complete rendered address and path parameters, and confirm that placeholder variables can be resolved into actual values.
- In the variables panel, check the source of each placeholder, check the request header names and value sources, and use one sample request to compare the returned fields.