What this category's data looks like
This category's data involves three core types of materials: talent training programs, course standards, and job competency analysis tables. Talent training programs are drafted by the academic affairs office or the specialty leader, course standards are written by the course leader, and job competency analysis tables are jointly filled in by specialty teachers and enterprise experts. All three types of materials contain fields, dates, and signatures: the program contains the specialty name, program length, and training objectives; the course standard contains the course name, class hours, and assessment method; the job competency analysis table contains the job name, competency items, and corresponding courses. In terms of update cadence, the program is revised by academic year, course standards are adjusted in sync with the program, and the job competency analysis table is updated every two years. When the materials enter the question-and-answer intake and missing-item follow-up function, the program serves as the main file, the course standards serve as support, and the job competency analysis table serves as the job basis.
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 intake records and the completed follow-up questions are parsed from the response by subsequent nodes, or handled and completed by an external system according to the agreement. The HTTP module sends requests to the target address; path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Talent training program | Fields include specialty name, program length, and training objectives; the date is the revision date; the signatures are those of the specialty leader and the academic affairs officer | Check whether the program name is consistent with the specialty name in the course standards, and inspect the revision date and signature fields |
| Course standard | Fields include course name, class hours, and assessment method; the date is the formulation date; the signature is that of the course leader | Compare the course name in the course standard with the corresponding course name in the job competency analysis table, and check the class hours and date |
| Job competency analysis table | Fields include job name, competency items, and corresponding courses; the date is the analysis date; the signatures are those of the enterprise expert and the specialty teacher | Check whether the job name corresponds to the training objectives in the talent training program, and inspect the correspondence between competency items and courses as well as the signatures |
| HTTP request | The request address and path parameter placeholder variables can be resolved into actual values; the request header authentication information is passed in according to the external system's requirements; the request body fields are consistent with the external interface agreement | View the fully rendered address in the request preview, check the request header names and value sources, compare the response using a sample request, and check the source of each placeholder in the variables panel |
Three common errors
- Symptom: The same specialty name is written differently in the talent training program and the course standard. Cause: The two materials are entered by different personnel, and name alignment and version synchronization were not performed.
- Symptom: The course class hours in the job competency analysis table do not match the class hours in the course standard. Cause: After the course standard was revised, the job competency analysis table was not updated in sync, and the versions were not synchronized.
- Symptom: The course standard lacks the course leader's signature or the enterprise receipt. Cause: No signature and receipt checks were set up in the material circulation step, and missing items were not identified at submission.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, and then compare the result against a sample. Check the value source of the Authorization request header, verify the origin of each placeholder in the variables panel, and confirm that the responseData returned fields are consistent with the external interface agreement.
Business test: submit a question that lacks key information and see whether it asks a follow-up question first before answering.
- In the variables panel, verify the source of each placeholder and confirm that the variables in the request address, request headers, and request body can all be resolved into actual values.
- Compare the response using a sample request, check the status code and returned fields, and confirm that the external system receives non-empty fields.