What this category's data looks like
This page addresses progress records and statistical reconciliation for journal publication licenses and annual verification. The materials come from three categories: journal publication licenses, annual verification forms, and rectification reports. The license provides the journal name, publication number, sponsoring organization, validity period, and issue date; the annual verification form provides the year, verification conclusion, handler, and submission date; the rectification report provides the issue items, rectification measures, completion date, and receipt signature. The three types of materials enter the workflow weekly or monthly, each playing a different role: the license is the master record of subject qualification, the verification form is the main record of annual progress, and the rectification report is the evidence of exceptions and closure. Field characteristics center on names, quantities, dates, signatures, and receipts, and the update rhythm follows verification batches and rectification milestones.
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 "progress table and statistical scope description" is parsed by subsequent nodes from the response, or handled by an external system according to the agreement to complete the next step. The HTTP module sends a request to the target address. Path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | Fields, dates, and signatures are consistent with the subject information in the verification form | In the request preview, view the fully rendered address and check whether the license's journal name, publication number, validity period, and issue date are passed in with the request body |
| Annual verification form | The number of records matches the statistical count, and the scope is stated in the header | Check the request header names and value sources, and confirm that the year, verification conclusion, handler, and submission date are sent according to the agreed fields |
| Rectification report | Issue items, rectification measures, completion date, and receipt signature are complete | Use a sample request to compare the response, and check whether the rectification report's name, quantity, date, and signature match the license and verification form |
| Variable source | Every placeholder can be traced to a specific origin | In the variable panel, check the source of each placeholder and confirm that the values of Authorization, variables, and responseData are traceable |
Three common errors
- Symptom: The journal name, quantity, and date of the same record do not match between the license and the verification form. Cause: The two materials are maintained separately and are not backfilled according to the same scope.
- Symptom: The rectification report version is not synchronized, and an old draft is sent with the request body. Cause: The external system does not return the version identifier as agreed, and the placeholder variable points to the old value.
- Symptom: The verification form lacks a signature or receipt, but the statistical total is still included. Cause: Exceptions are not marked separately, and the statistical scope is not stated in the header.
How to verify the setup
This feature acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that the values of Authorization, variables, and responseData are consistent in the request headers, request body, and response.
Business test: use one week of records to check the total, see whether the scope and exceptions are clearly stated, and whether the number of records matches the statistical count.
- Check the request address and path parameters, confirm that placeholder variables can be resolved into actual values, and view the fully rendered address in the request preview.
- Check the request header names and value sources, confirm that authentication information is passed in according to the external system's requirements, and that the request body fields are consistent with the external interface agreement.