What this category's data looks like
This category's data involves three types of materials: school-enterprise cooperation agreements, order class training plans, and master-apprentice mentoring records. School-enterprise cooperation agreements are signed by the school and the partner enterprise, and the fields include the cooperation start and end dates, and signatures and seals of both parties; order class training plans are jointly compiled by the school and the organizer, and the fields include class name, number of students, course modules, and version number; master-apprentice mentoring records are filled in weekly by the mentoring master, and the fields include apprentice name, mentoring content, date, and signatures of both parties. Materials are updated by semester or batch, and after an agreement is changed, the training plan and mentoring records must have synchronized versions. When entering the Q&A intake and missing-item follow-up function, the cooperation agreement serves as the qualification basis, the training plan serves as the class and course basis, and the mentoring records serve as the process basis; together the three support question answering and missing-item identification.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, and outputs the response body, status code, and returned fields. The "intake records and completed question items" 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 a request to the target address, and variables can be used as placeholders in all three places: path parameters, request body, and request headers. Variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| School-enterprise cooperation agreement | Check whether the cooperation start and end dates, and the signatures and seals of both parties are complete, and whether the name is consistent with the order class training plan | View the fully rendered address in the request preview, compare the returned fields with a sample request, and check the Authorization request header and the responseData field |
| Order class training plan | Check the class name, number of students, course modules, and version number, and whether the name, quantity, and date of the same record match between the agreement and the plan | Check the source of each placeholder in the variables panel, and confirm that the variables values are consistent with the external interface agreement |
| Master-apprentice mentoring record | Check the apprentice name, mentoring content, date, and signatures of both parties, whether the version is synchronized with the training plan, and whether the receipt is missing | Compare the return with a sample request, confirm that the fields are consistent with the external interface agreement, and that the status code and returned fields meet expectations |
| Intake records and completed question items | Check whether missing items are identified and followed up, whether answers are based on materials, and whether they are forwarded to the organizer for handling | Ask a question that lacks key information, and see whether it follows up first before answering |
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 materials were entered separately, and no cross-check was performed.
- Symptom: The training plan has been updated, but the mentoring records still use the old version. Cause: The version was not synchronized, and the change receipt is missing.
- Symptom: The mentoring records lack the signature of the master or the apprentice. Cause: The paper records were not returned in time, and the receipt is missing.
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 a sample, and confirm that the values and sources of Authorization, variables, and responseData are consistent.
Business test: ask a question that lacks key information, and see whether it follows up first before answering.
- Check the source of each placeholder in the variables panel, and confirm that global variables, system variables, or preceding node outputs can be resolved into actual values.
- Compare the return with a sample request, and check that the request header names and value sources, and the request body fields, are consistent with the external interface agreement.