What this category's data looks like
This page focuses on Q&A acceptance and missing-item follow-up for journal publication licenses and annual verification. The materials include the journal publication license, the annual verification form, and the rectification report. The license states the name, publication number, and validity period; the verification form records annual data and personnel information; the rectification report corresponds to problem items and receipts. The materials come from submissions by publishing units and system aggregation, and are updated by year or by rectification cycle. When the materials enter this function, the license and the verification form serve as the comparison baseline, and the rectification report serves as the trigger source for missing-item follow-up questions. The field characteristics center on names, quantities, dates, and signatures, and the same record must be aligned item by item across multiple materials.
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 "acceptance record and completed question items" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest. The request URL, request headers, and request body can all reference global variables, system variables, or outputs from preceding nodes via variables, and authentication information is placed in Authorization according to the external system's requirements.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | Whether the name, publication number, and validity period are consistent with the verification form | Render the URL in the request preview, and check the responseData returned fields against the license fields item by item |
| Annual verification form | Whether the annual data, dates, and signatures are complete and aligned with the license | Compare the response using one sample request, and check whether fields with missing signatures or receipts are identified |
| Rectification report | Whether the problem items and receipt dates are synchronized with the verification form version | Check the request body fields against the external interface agreement, and confirm that the name, quantity, and date of the same record are consistent |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the license and the verification form. Cause: The two materials were entered separately, without field-level comparison and receipt verification.
- Symptom: The rectification report version is not synchronized, and follow-up questions are based on old-version items. Cause: After the material was updated, re-parsing was not triggered, and the version identifier was not passed in with the request.
- Symptom: The request returns 401, and the acceptance record cannot be generated. Cause: The source of the
Authorizationvalue is wrong, or the authentication information was not passed in according to the external system's requirements.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample. Check that every placeholder in variables can be traced to its source, and that the responseData fields are consistent with the sample.
Business test: submit a question that lacks key information, and see whether it asks a follow-up question first before answering.
- In the variables panel, check the source of each placeholder, and confirm that the request URL and path parameters can be resolved into actual values.
- Check the request header names and value sources, and use one sample request to compare the returned fields against the external interface agreement.