What this category's data looks like
In the journal three-review-three-proof and editorial quality scenario, the core materials include three types: three-review forms, proofs, and proofreading records. The three-review forms carry the fields, dates, and signatures of initial review, re-review, and final review; the proofs carry the textual and formatting changes after each round of proofreading; the proofreading records carry the proofreading rounds, error types, and responsible person receipts. The three types of materials come from scattered sources, and their update rhythm advances according to review rounds and proofreading rounds, with field characteristics mainly consisting of names, quantities, dates, signatures, and version numbers. When entering the workflow, the three-review forms serve as the traceability starting point, the proofs serve as the comparison base, and the proofreading records serve as the review evidence; together, the three support the generation of the exception list and review conclusions.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The "exception list and review conclusions" are completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Three-review form | Whether the fields, dates, and signatures are complete, and whether the names, quantities, and dates can match those in the proofs and proofreading records | Check the options and branch connections one by one in the node, and use variables to compare the names, quantities, and dates of the three-review form and the proofreading records |
| Proof | Whether the version is synchronized, and whether the changes have corresponding proofreading records and signature receipts | Trigger a user selection once, check the node status in the run record, and use nodeId to locate whether the proof version and the proofreading records are consistent |
| Proofreading record | Whether the source material can be traced when signatures or receipts are missing, and whether the names, quantities, and dates of the same record are consistent across the two materials | Reference the selection result variable in a subsequent node and run a test once, and check the signatures and receipts of the proofreading records and the three-review form |
| User selection node | Each option corresponds to one branch, and whether the process continues downward after the interaction is completed | Test each option one by one, and check the branch direction and interaction status in the run record |
Three common errors
- Phenomenon: The names, quantities, and dates of the same record do not match between the three-review form and the proofreading records. Cause: The two materials are entered separately, lacking cross-material field comparison and version synchronization.
- Phenomenon: The proof version is not synchronized, and the corresponding proofreading records and signature receipts cannot be found for the changes. Cause: The version number is not updated with the review rounds and proofreading rounds, and version verification is not performed when the materials enter the workflow.
- Phenomenon: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections are not checked one by one, and the selection result variable is not passed to subsequent nodes.
How to verify the setup
Acceptance of this function: test each option one by one, check the branch direction and interaction status in the run record, and confirm that variables has been passed to subsequent nodes.
Business test: create an exception record, see whether the source material can be traced, and check the fields, dates, and signatures of the three-review form, proofs, and proofreading records.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference the selection result variable in a subsequent node and run a test once, and check the interaction status record corresponding to
nodeId.