What this category's data looks like
Materials for continuing education credit hour recognition usually include a course filing form, a study certificate, and a credit hour recognition form. The course filing form is used to check the course name, organizing unit, number of class hours, and filing date; the study certificate is used to check the learner's name, ID document number, study start and end dates, and assessment result; the credit hour recognition form is used to check the recognized credit hours, recognition date, and handler's signature. When these three types of materials enter this function, the course filing form and study certificate serve as the attachment basis for Q&A intake, while the credit hour recognition form serves as the comparison baseline for missing-item follow-up. Materials are mostly uploaded by the handler in batches, and the update rhythm changes with the training cycle. The field characteristics appear as the cross-occurrence of four types of information: names, quantities, dates, and signatures, and the same record is prone to mismatching across the two 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 "intake records and items to be completed" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest. The request URL, path parameters, request headers, and request body can all reference global variables, system variables, or outputs from preceding nodes through variables, and the returned content is received as responseData.
| Object | Check | Verification action |
|---|---|---|
| Course filing form | The course name, number of class hours, and filing date are consistent across the three materials, and the signature and receipt are complete | Compare the name, quantity, and date field by field between the course filing form and the study certificate, and check the signature field |
| Study certificate | The learner's name, study start and end dates, and assessment result can support the credit hour recognition form | View the fully rendered URL in the request preview, and check the request header names and the sources of their values |
| Credit hour recognition form | The recognized credit hours, recognition date, and handler's signature match the filing form and study certificate | Use one sample request to compare the response, and confirm that the returned fields are consistent with the external interface agreement |
| Variable sources | Every placeholder can be traced to a specific origin, and authentication information is passed in according to the external system's requirements | Check the source of each placeholder in the variables panel, and check the source of the Authorization value |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match across the two materials. Cause: The course filing form and study certificate are entered separately, lacking cross-comparison.
- Symptom: The version is not synchronized, and an old version of the credit hour recognition form is still referenced. Cause: The attachment was not replaced after the material was updated, and Q&A intake still takes the old version.
- Symptom: A signature or receipt is missing, so the recognition form cannot serve as a basis. Cause: The handler did not check the signature field and receipt attachment when uploading.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample; confirm that the variables placeholders resolve to actual values and that the fields returned by responseData are consistent with the agreement.
Business test: submit a question that lacks key information, and see whether it asks a follow-up question before answering.
- View the fully rendered URL in the request preview, and check the request header names and the sources of their values.
- Check the source of each placeholder in the variables panel, and use one sample request to compare the response.