What this category's data looks like
Journal publishing licenses and annual verification involve three types of materials: journal publishing license, annual verification form, and rectification report, all of which contain fields, dates, and signatures. The license records the journal name, journal number, sponsoring organization, and validity period; the verification form records annual data, personnel, and business operations; the rectification report records issues, measures, and receipts. The materials come from documents issued by the competent authority, internal reporting, and external receipts, and the update cadence advances according to annual verification and rectification deadlines. When entering this function, the license and verification form serve as the baseline source for the version ledger, and the rectification report serves as the trigger item for change records; together, the three determine that the current version is unique, old versions are traceable, and references are synchronized. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures. Any inconsistency will affect the version determination.
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 and then completed. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Journal publishing license | Whether the fields, dates, and signatures are consistent with the verification form | Compare the journal name, journal number, validity period, and issue date, and check whether the signature and receipt are complete |
| Annual verification form | Whether the names, quantities, and dates of the same record match in the two materials | Check the annual data and license fields item by item, and mark discrepancies |
| Rectification report | Whether the version is synchronized and whether the reference points to the current version | Check the report version number and reference link, and confirm that the old version is traceable |
| HTTP request | Whether the placeholder variables can be resolved into actual values, and whether the authentication information is passed in according to the external system's requirements | View the fully rendered address in the request preview, check the request header names and value sources, and compare the response with a sample request |
Three common errors
- Symptom: The names, quantities, and dates of the same record do not match between the license and the verification form. Cause: The two materials are filled in separately, without field-level comparison and version alignment.
- Symptom: The rectification report has been updated, but the reference still points to the old version. Cause: The version is not synchronized, and the reference link is not updated with the version number.
- Symptom: Materials are missing signatures or receipts. Cause: The circulation step is not closed-loop, and signatures and receipts are not archived together with the version.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, and then compare the result against a sample; check whether the Authorization request header, the variables variable sources, and the responseData returned fields are consistent.
Business test: change one piece of content and see whether the version number and reference are updated synchronously.
- In the variables panel, check the source of each placeholder and confirm that the variables in the path parameters, request body, and request headers can all be resolved.
- Use a sample request to compare the response, and check that the request body fields are consistent with the external interface agreement.