What this category's data looks like
This category's data covers three types of materials: internship agreements, internship plans, and internship logs. Agreements are signed by three parties—the school, the enterprise, and the student—and their fields include position, term, insurance, and signatures; plans are prepared by supervising instructors and include rotation arrangements, week numbers, and task objectives; logs are filled in by students daily and include date, work hours, content, and supervisor signature. The three types of materials are summarized weekly into a progress table, with the statistical definitions written in the table header, such as "expected attendance", "actually on duty", and "number of logs". The update cadence is daily for logs, weekly for plans, and per semester for agreements. When the materials enter this feature, agreements and plans provide baseline fields and signature status, while logs provide item-by-item records, which are used to reconcile against the statistics.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The "progress table and statistical definition notes" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest. The HTTP module sends requests to the target address, and variables can be used as placeholders in all three places: path parameters, request body, and request headers. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Request address and path parameters | Placeholder variables can resolve to actual values | View the fully rendered address in the request preview, and verify the source of variables |
| Request headers | Authentication information is passed in according to the external system's requirements | Verify the request header names and the source of their values, and confirm how Authorization is written |
| Request body | Fields are consistent with the external interface's agreement | Compare the response using a sample request, and verify the responseData fields |
| Internship logs | Date, work hours, signature, and statistical definitions are consistent | Reconcile the number of logs with the progress table totals weekly, and check for missing signatures or receipts |
Three common errors
- Symptom: the position name for the same record does not match between the agreement and the log. Cause: the two materials are entered separately and are not summarized after mapping to unified fields.
- Symptom: the plan version is not synchronized, and the week numbers and task objectives are still the old version. Cause: after updating, the request was not triggered again, and the variables still take the old output of the preceding node.
- Symptom: logs are missing the supervisor signature or receipt, but the statistics still include them in the totals. Cause: the definitions do not state exception handling in the table header, and invalid records are not excluded during reconciliation.
How to verify the setup
Feature acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that responseData and variables are parsed correctly.
Business test: reconcile the totals using one week of records, and check whether the definitions and exceptions are clearly stated.
- In the variables panel, verify the source of each placeholder, and confirm that the variables in all three places—request address, request headers, and request body—can be traced to global variables, system variables, or the output of preceding nodes.
- Use a sample request to compare the returned fields, and verify whether the fields, dates, and signatures of the internship agreement, internship plan, and internship log are consistent with the statistical definition notes.