What this category's data looks like
The initial review of academic journal submissions involves three types of materials: submitted manuscripts, author information forms, and plagiarism check reports. Submitted manuscripts are provided by authors and include title, author signatures, affiliation, date, and signature field; author information forms are registered by the editorial office and include author names, order, affiliation, contact information, and receipt; plagiarism check reports are generated by the detection system and include similarity rate, detection date, and number. Materials are updated with submission batches and checked item by item during the initial review stage. When entering workflow orchestration, the submitted manuscript serves as the main record to trigger the process, the author information form is used to verify signatures and order, and the plagiarism check report serves as an attachment for branch decisions. The three must be consistent in name, quantity, and date; version synchronization and signed receipts are prerequisites for initial review release.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "External entry points and authorization scope" are completed by subsequent nodes continuing execution along the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow state; after the user completes the selection, the branch corresponding to the chosen option continues execution.
| Object | Check | Verification action |
|---|---|---|
| Submitted manuscript | Whether title, author signatures, affiliation, date, and signature field are complete and consistent item by item with the author information form | Compare names and quantities against the author information form, check the signature field and date, and record inconsistencies |
| Author information form | Whether author names, order, affiliation, contact information, and receipt are consistent with the submitted manuscript and whether versions are synchronized | Compare field by field with the submitted manuscript, confirm receipt and signature, and mark version differences |
| Plagiarism check report | Whether similarity rate, detection date, and number correspond to the submitted manuscript and whether the report is complete | Check the report number against the manuscript number and verify whether the detection date falls within the initial review period |
| User selection node | Whether options correspond one-to-one with branches and whether interaction state and selection result variables are passed | Test each option individually, view branch directions and interaction state in the run record, and verify references to variables and nodeId |
Three common errors
- Symptom: The same author's name or order does not match between two materials. Cause: The author information form was not updated in sync with the submitted manuscript version, and changes were missed during registration.
- Symptom: The detection date of the plagiarism check report is inconsistent with the manuscript submission date. Cause: The report version was not synchronized, and an old report was mistakenly used as the attachment for the current batch.
- Symptom: The signature field or receipt is missing, yet the initial review still proceeds. Cause: Signatures and receipts were not verified when materials were received, and the workflow branch did not intercept.
How to verify the setup
Feature acceptance: Test each option individually, check the branch directions and interaction state in the run record, and confirm that variables and nodeId references are correct.
Business test: Access once with a restricted identity and see whether the visible scope matches the setting.
- In the user selection node, check each option and branch connection one by one, trigger once, and view the node status in the run record.
- In subsequent nodes, reference the selection result variable and run a test once, checking the branch direction and interaction state record.