What this category's data looks like
This category's data involves three types of materials: course filing forms, study certificates, and credit recognition forms. Course filing forms record the course name, number, credit hours, filing date, and handler's signature; study certificates record the learner's identity, course name, completion date, and issuing unit's seal; credit recognition forms summarize the course name, recognized credit hours, recognition date, and review signature. Materials are submitted in batches by teaching sites or training institutions, and the update cadence is typically centralized reporting after each course period ends. The field characteristics center on names, quantities, dates, and signatures. When entering the authorized access and external services function, course filing forms are used to verify whether a course can be recognized, study certificates are used to check individual completion records, and credit recognition forms are used to generate externally visible recognition results; the names, quantities, and dates in all three must be consistent, and signatures or receipts must be complete. Otherwise, the visible scope and authorization scope of the external entry point cannot match.
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 externally available entry point and authorization scope are parsed from the response by subsequent nodes, or handled by an external system according to the agreement. The HTTP module sends a request to the target address. Variables can be used as placeholders in the path parameters, request body, and request headers. Variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Course filing form | The course name, number, credit hours, and filing date must match the study certificate and credit recognition form item by item, and the handler's signature must be complete | Compare the course name, credit hours, and date for the same course across the three materials; check the signature and receipt, access once with a restricted identity, and see whether the visible scope matches the configured setting |
| Study certificate | The learner's identity, course name, and completion date must correspond to the course filing form and credit recognition form, and the issuing unit's seal must be complete | In the request preview, view the fully rendered address, check the source of the Authorization request header value, and confirm that each placeholder in variables can be traced to a specific origin |
| Credit recognition form | The recognized credit hours, recognition date, and review signature must be consistent with the course filing form and study certificate, and the version must be the latest | Use a sample request to compare the response, check that the fields returned in responseData match the agreement, and confirm that there are no missing signatures or receipts |
| Request body fields | The fields must match the agreement with the external interface, and empty fields must not enter the external entry point | Use a sample request to compare the response, and check that the field names, quantities, and dates are consistent with the materials |
Three common errors
- Symptom: The course name, credit hours, or date for the same record do not match between the course filing form and the study certificate. Cause: The two materials were entered separately, without item-by-item comparison and version synchronization.
- Symptom: The credit recognition form lacks a review signature or receipt, but the external entry point is still open according to the default scope. Cause: The material circulation step did not verify the completeness of signatures and receipts.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: Authentication information was not passed in as required by the external system, or variable placeholders were not resolved into actual values.
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; confirm that the values and sources of Authorization, variables, and responseData are traceable.
Business test: access once with a restricted identity and see whether the visible scope matches the configured setting; unauthorized content must not be visible, and the visitor's identity must match the visible scope.
- In the variables panel, check the source of each placeholder and confirm that the variables in the path parameters, request body, and request headers come from global variables, system variables, or the output of preceding nodes.
- Check the request header names and value sources, use a sample request to compare the response, and confirm that the fields match the agreement with the external interface.