What this category's data looks like
Journal publication licenses and annual verification circulate in the technical center as three types of materials: the journal publication license, the annual verification form, and the rectification report. The license comes from the licensing decision document, and its fields include name, publication period, publishing unit, license number, and validity period; the annual verification form is updated by verification year, and its fields include verification conclusion, verification date, and handler signature; the rectification report is generated with verification exceptions, and its fields include rectification items, completion date, and review signature. When the materials enter the exception tracing and manual review function, the license serves as the subject identity baseline, the annual verification form serves as the basis for periodic status, and the rectification report serves as the evidence for exception handling. The three are cross-compared by the name, quantity, date, and signature of the same record to form an exception list and review conclusion.
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" is parsed from the response by subsequent nodes, or handled and completed by an external system according to the agreement. Variables can be used as placeholders in three places: the request URL and path parameters, request headers, and request body. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | The name, license number, validity period, and publishing unit are consistent between the license and the annual verification form | Check the placeholder sources in the variables panel, use the request preview to see the rendered URL and fields, and compare the names and dates in the two materials |
| Annual verification form | The verification conclusion, verification date, and handler signature are complete, and the version is synchronized with the license | Check the request header names and value sources, use a sample request to compare the returned fields, and check whether the signature and receipt are missing items |
| Rectification report | The rectification items, completion date, and review signature can be traced back to the source record | Check whether the fields returned by responseData include the rectification items and date, and compare them one by one against the license and verification form |
| HTTP request | The placeholder variables in the path parameters, request body, and request headers can all be parsed into actual values | View the complete rendered URL in the request preview, and check the sources of Authorization and variables |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the license and the annual verification form. Cause: The two materials are entered separately and are not cross-compared for the same record.
- Symptom: The version of the annual verification form is not synchronized, and old-version fields still participate in the comparison. Cause: The materials are updated at different paces, and the placeholder variables retrieve old output from preceding nodes.
- Symptom: The rectification report lacks a signature or receipt, and the exception cannot be closed. Cause: The review step does not write back the signature field, and the external system does not return a receipt as agreed.
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 the placeholders in responseData, Authorization, and variables are all parsed into actual values.
Business test: create an exception record and see whether it can be traced to the source materials, that is, from the returned fields to the original records in the journal publication license, annual verification form, and rectification report.
- In the request preview, check the complete rendered URL, request header names, and request body fields, and match each item back to the placeholder sources in the variables panel.
- Use a sample request to compare the returned fields with the external interface agreement, and confirm that the exception list and review conclusion can be handed to the responsible person for handling.