What this category's data looks like
Continuing education credit recognition materials usually include three types: course filing forms, study certificates, and credit recognition forms. The course filing form records the course name, filing number, number of credit hours, and course start date; the study certificate is issued by the training institution and states the learner's name, course name, study start and end dates, and assessment result; the credit recognition form is filled out by the employer or competent authority and summarizes the recognized credit hours, recognition date, and handler's signature. When these three types of materials enter the exception tracing and manual review function, their roles differ: the course filing form is used to compare the course name and filed credit hours, the study certificate is used to verify the actual study dates and quantity, and the credit recognition form is used to confirm the recognition conclusion and signed receipt. Material sources are mostly external system pushes or manual uploads, and the update rhythm changes with course batches and recognition cycles. The field characteristics are concentrated in four places: name, quantity, date, and signature.
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 exception list and review conclusion are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the next step. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Course filing form | The course name, filing number, number of credit hours, and course start date must be consistent with the study certificate | Retrieve the original record of the filing form, compare the name, quantity, and date fields, and check whether the filing number is traceable |
| Study certificate | The study start and end dates, assessment result, and receipt from the training institution must be complete | Check the dates and quantity on the study certificate, verify whether the signature or receipt is missing, and compare item by item with the filing form |
| Credit recognition form | The recognized credit hours, recognition date, and handler's signature must be supported by original records | Inspect the signature field and date field on the recognition form, compare with the quantity on the study certificate, and confirm whether the version is synchronized |
| HTTP request | The placeholder variables in the request URL and path parameters can be resolved into actual values | View the fully rendered URL in the request preview, and check the source of variables and the value of Authorization |
Three common errors
- Symptom: The course name and number of credit hours for the same record do not match between the course filing form and the study certificate. Cause: The two materials are entered at different stages, and there is a lack of field-by-field comparison and source tracing.
- Symptom: The credit recognition form has been signed, but the version of the study certificate has not been synchronized, and the dates and quantity are still the old version. Cause: After the material was updated, re-verification was not triggered, and the version identifier did not flow with the record.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The source of the
Authorizationvalue was not checked, and the request body fields are inconsistent with the external interface agreement.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that responseData and variables are traceable.
Business test: create an exception record, see whether the source material can be traced, and verify the name, quantity, date, and signature across the course filing form, study certificate, and credit recognition form.
- In the variables panel, check the source of each placeholder and confirm that the placeholders in the request URL, request headers, and request body can all be traced to global variables, system variables, or outputs from preceding nodes.
- Use a sample request to compare the response, check whether the request body fields are consistent with the external interface agreement, and record the number of array items and the tokens of the referenced text.