What this category's data looks like
This category's data involves three types of materials: course filing forms, study certificates, and hour recognition forms. Course filing forms come from training institutions' filings and record the course name, number of hours, start date, and signature of the person in charge; study certificates are issued by the teaching unit and include the learner's name, course name, completed hours, and seal; hour recognition forms are filled out by the employer or competent authority and include recognized hours, recognition date, and approval signature. The three types of materials are updated at different rhythms: filing forms change with course plan adjustments, study certificates are issued by batch, and recognition forms are summarized by application cycle. When the materials enter this feature, the course filing form serves as the source of basic course information, the study certificate serves as the learner's completion evidence, and the hour recognition form serves as the final basis for recognition. The version ledger needs to record each material's current version number, effective date, and change description; old versions are retained for traceability, and references are updated in sync. In terms of field characteristics, names, quantities, dates, and signatures are the key points for verification, and the same record should remain consistent across the three materials.
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 "version ledger and change records" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the next step. The request URL, path parameters, request headers, and request body can all reference global variables, system variables, or outputs from preceding nodes via variables, and authentication information is placed in Authorization according to the external system's requirements.
| Object | Check | Verification action |
|---|---|---|
| Course filing form | The course name, number of hours, start date, and signature of the person in charge are consistent across the three materials | Check the course name and hours fields in responseData, and compare the corresponding values in the study certificate and recognition form |
| Study certificate | The learner's name, completed hours, issue date, and seal are complete, and match the course information in the filing form | Check the name and hours in the returned fields, and confirm there is no difference in name or quantity from the filing form and recognition form |
| Hour recognition form | The recognized hours, recognition date, and approval signature are complete, and the current version is referenced | View the recognized hours and version number in responseData, and confirm the reference points to the latest filing form and study certificate |
| HTTP request configuration | The request URL, path parameters, request headers, and placeholder variables in the request body can all be resolved to actual values | In the request preview, check the rendered complete URL, the source of the Authorization value, and the request body fields |
Three common errors
- Symptom: The same learner's course name is written differently in the filing form and the study certificate. Cause: The two materials were entered separately and were not updated in sync based on the current version.
- Symptom: The study certificate referenced by the hour recognition form is still an old version, and the recognized hours do not match the quantity in the latest certificate. Cause: The version ledger did not record the change, and the reference was not synchronized with the version number.
- Symptom: The external system returns empty fields or the request returns 401. Cause: The authentication information in the request header was not passed in according to the agreement, or the request body fields are inconsistent with the interface agreement.
How to verify the setup
Feature acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample; confirm that all variables placeholders are resolved to actual values, and that the name, quantity, date, and signature fields in responseData match the sample.
Business test: change one piece of content and see whether the version number and references are updated in sync; record the change description in the version ledger, and confirm that the old version is traceable and the reference points to the current version.
- In the variables panel, check the source of each placeholder variable, confirm it comes from a global variable, system variable, or output from a preceding node, and check the rendered complete URL and request body fields in the request preview.
- Use one sample request to compare the response, check the status code and returned fields; check whether the names, quantities, dates, and signatures in the course filing form, study certificate, and hour recognition form are consistent, and whether the version number and references are synchronized.