What this category's data looks like
This page addresses the preliminary review scenario for academic journal submissions, and the materials include three types: the submitted manuscript, the author information form, and the plagiarism check report. The submitted manuscript provides the main text and bibliographic information, the author information form carries the authorship, affiliation, order, and signature, and the plagiarism check report gives the similarity rate and detection time. The materials come from the author submission and the editorial office receipt stages, and updates change with revised manuscripts, supplementary materials, or version replacements. The field characteristics center on names, quantities, dates, and signatures: manuscript title, author name, affiliation name, funding number, manuscript number, receipt date, detection date, signature or receipt. When entering the Q&A intake and missing-item follow-up function, the three types of materials each play a different role: the manuscript is used to compare the bibliographic information and main text, the author information form is used to verify authorship and order, and the plagiarism check report is used to verify the detection conclusion and time. The three need to be aligned on the same record, and if any field does not match, a follow-up question is triggered.
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 intake record and the completed question items are parsed from the response by subsequent nodes, or handled externally according to the agreement to finish the process. The HTTP module sends a request to the target address, and variables can be used as placeholders in three places: path parameters, request body, and request headers. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Submitted manuscript | Whether the title, manuscript number, and receipt date are consistent with the author information form and the plagiarism check report | In the request preview, view the fully rendered address, and check the request body fields against the external interface agreement |
| Author information form | Whether the authorship, affiliation, order, date, and signature or receipt are complete | Check the request header names and value sources, and confirm that authentication information is passed in according to the external system's requirements |
| Plagiarism check report | Whether the detection time, similarity conclusion, and manuscript version are synchronized | In the variables panel, check the source of each placeholder, and confirm that variables can be traced to a specific origin |
| HTTP node output | Whether the status code and returned fields can be parsed by subsequent nodes | Use a sample request to compare the response, and check the responseData field structure |
Three common errors
- Symptom: The name and date of the same manuscript do not match between the author information form and the plagiarism check report. Cause: The two materials were submitted separately and the fields were not aligned on the same record.
- Symptom: The revised manuscript has been replaced, but the plagiarism check report still points to the old version. Cause: The version was not synchronized, and the detection time was not bound to the manuscript version.
- Symptom: The external system receives empty fields or the request returns 401. Cause: The request header authentication information is missing, or the request body fields are inconsistent with the agreement.
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 a sample; check the Authorization request header, the variables source, and the responseData structure.
Business test: submit a question missing key information and see whether it asks a follow-up question before answering.
- In the request preview, confirm that the placeholder variables in all three places—path parameters, request body, and request headers—are resolved to actual values.
- In the variables panel, check the source of each placeholder and confirm that it comes from a global variable, a system variable, or the output of a preceding node.