What this category's data looks like
Materials for journal three-stage review and three-proofreading and editorial quality mainly consist of three-stage review forms, proofs, and proofreading records, coming from each stage of the editorial process and updated with version iterations and issuance milestones. The three-stage review form records the opinions and signature dates of initial review, re-review, and final review; the proof carries the post-typesetting text and layout; the proofreading record retains each proofreading trace and receipt. When the materials enter the exception tracing and manual review function, the three-stage review form serves as the basis for the chain of responsibility, the proof serves as the base copy for content comparison, and the proofreading record serves as the process evidence. The fields, dates, and signatures of the three need to be aligned item by item, to locate differences in names, quantities, and dates of the same record across different materials, and to identify situations where versions are not synchronized and signatures or receipts are missing, forming an exception list and review conclusion.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The "exception list and review conclusion" is parsed by subsequent nodes from the response, or handled by an external system according to the agreement to complete the follow-up. The placeholder variables in the request URL, request headers, and request body come from global variables, system variables, or outputs of preceding nodes, and the rendered result can be checked in the request preview.
| Object | Check | Verification action |
|---|---|---|
| Three-stage review form | Whether the fields and signature dates of initial review, re-review, and final review are complete, and whether the name and quantity of the same record are consistent with the proof | Check the source of variables in the variable panel, and use the request preview to see the complete rendered URL and request body fields |
| Proof | Whether the version number and typesetting date are synchronized with the proofreading record, and whether missing signatures or receipts are marked | Use a sample request to compare the response, and check the fields in responseData against the actual content of the proof |
| Proofreading record | Whether each proofreading trace, receipt, and date can be traced back to the source material, and whether the name and quantity match | Check the request header Authorization and the source of its value, and confirm that the authentication information is passed in according to the external system's requirements |
| Exception list and review conclusion | Whether the exception is supported by original records, and whether the reviewer's signature is complete | Check the status code and returned fields in the request preview, then compare the result against a sample |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the three-stage review form and the proof. Cause: The two materials were not updated synchronously according to the same version, and the field sources are inconsistent.
- Symptom: The proofreading record lacks a signature or receipt, and the exception cannot be traced back to the source material. Cause: The process node did not backfill the signature information, and the receipt was not archived with the version.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The request header authentication information was not passed in according to the external system's requirements, and the variable placeholders were not resolved into actual values.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against a sample; at the same time, check the placeholder sources of variables, responseData, and Authorization.
Business test: create an exception record and see whether it can be traced back to the source material
- In the variable panel, check the source of each placeholder and confirm that the variables in the request URL, request headers, and request body can be resolved into actual values.
- Use a sample request to compare the response, check that the request body fields are consistent with the external interface agreement, and record the returned fields and status code.