What this category's data looks like
For modern apprenticeship and order class management, materials mainly come from school-enterprise cooperation agreements, order class training plans, and master apprenticeship records. School-enterprise cooperation agreements define the rights and responsibilities of the school and enterprise, the cooperation period, and signatures and seals; order class training plans list courses, job rotations, and assessment milestones; master apprenticeship records document apprenticeship content, work hours, and master signatures on a weekly or monthly basis. When materials enter the authorized access and external services function, the agreement and training plan serve as the authorization basis for external entry points, determining the classes, progress, and assessment scope visible to parents or superiors; apprenticeship records serve as process materials and are made available for query within the authorized scope. The update rhythm follows agreement renewals, plan revisions, and apprenticeship record archiving. Field characteristics are name, quantity, date, and signature, and each document must be aligned individually.
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 points and authorization scope are completed by subsequent nodes parsing the response, or by external systems handling it according to the agreement.
| Object | Check | Verification action |
|---|---|---|
| School-enterprise cooperation agreement | Name, quantity, date, and signature are consistent between the agreement and the training plan | Compare the cooperating enterprise name, order class quantity, signing date, and seal position in the two documents, and check whether the request body fields are consistent with the external interface agreement |
| Order class training plan | Courses, job rotations, and assessment milestones are consistent between the plan and the apprenticeship records | View the rendered full address in the request preview, and check whether the path parameters and the class name, course quantity, and assessment date in the request body correspond |
| Master apprenticeship record | Apprenticeship content, work hours, and master signature are consistent between the record and the plan | Check the request header names and value sources, pass authentication information using Authorization, and inspect whether the master signature and receipt in the record are complete |
| Variable source | Every placeholder can be traced to a specific origin | Check the sources of placeholders such as variables and responseData in the variable panel, and confirm whether they come from global variables, system variables, or outputs of preceding nodes |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the agreement and the training plan. Cause: The two documents were revised separately without cross-checking.
- Symptom: The apprenticeship record lacks the master signature or receipt. Cause: The signature page was not collected as agreed during archiving, or the receipt was not synchronized with the record.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: Authentication information was not passed in as required by the external system, or placeholder variables were not parsed into actual values.
How to verify the setup
In the request preview, view the rendered full address and check whether the path parameters and request body fields are parsed into actual values.
Check the request header names and value sources, and use a sample request to compare the returned fields with the external interface agreement.
- Preview the rendered request, check the status code and returned fields, and then compare the results against a sample.
- Use a restricted identity to access once and see whether the visible scope matches the settings.