What this category's data looks like
This page addresses the journal three-stage review and three-proof checking and editorial quality scenario; the materials come from three categories: three-stage review sheets, proofs, and proofreading records. The three-stage review sheet carries the fields, dates, and signatures of the initial review, re-review, and final review; the proof carries the version identifier, revision marks, and receipt; the proofreading record carries the proofreading rounds, quantities, and signatures. The materials are updated according to the manuscript circulation rhythm, and a new version is formed after each round of review and proofreading. When entering the authorized access and external services function, the three-stage review sheet is used to determine the completeness of the review stages and the completeness of signatures, the proof is used to determine whether the version is synchronized, and the proofreading record is used to determine whether the proofreading rounds and quantities are consistent. The three categories of materials each correspond to fields in the form, which the visitor fills in or confirms according to identity, forming an externally available entry point and authorization scope. The field characteristics are concentrated in names, quantities, dates, signatures, and version identifiers, and must be checked item by item.
Configuration and implementation checks
This link is executed by the form input node (interaction node) in the workflow, outputting the field values filled in by the user (passed to subsequent nodes after submission). The externally available entry point and authorization scope are then completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters an interactive state and the workflow state is recorded; after the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Three-stage review sheet | Whether the fields, dates, and signatures of the initial review, re-review, and final review are complete, and whether they are consistent with the names, quantities, and dates in the proof and proofreading record | Check the field names and required markers one by one in the formInput node configuration, and after submission check whether subsequent nodes can retrieve the corresponding field values |
| Proof | Whether the version identifier is synchronized with the three-stage review sheet and proofreading record, and whether the revision marks and receipt are complete | Check the version field name and required settings in the formInput node configuration, and after a trial run confirm that subsequent nodes retrieve the version identifier |
| Proofreading record | Whether the proofreading rounds, quantities, dates, and signatures match those in the three-stage review sheet and proof | Check the rounds and quantities fields in the formInput node configuration, and after submission check the field values retrieved by subsequent nodes |
| Form input node | Whether submission is possible when required items are empty, and whether the conversation continues to execute downward after submission | Use userSelect to select a restricted identity and run a trial once, checking the required markers and the field passing after submission |
Three common errors
- Symptom: The names, quantities, and dates of the same record do not match between the three-stage review sheet and the proofreading record. Cause: The fields in the two places were not checked item by item, and a different set of standards was used when filling in each.
- Symptom: The proof version is not synchronized; the three-stage review sheet has been updated while the proof is still the old version. Cause: The version identifier field was not confirmed in the form, and subsequent nodes retrieved the old value.
- Symptom: The three-stage review sheet lacks the final review signature or the proof lacks the receipt. Cause: Key material fields were not marked as required, and empty values were not intercepted at submission.
How to verify the setup
This function's acceptance: fill in once and submit, check whether the field values retrieved by subsequent nodes are consistent with the filled-in content, whether submission is possible when required items are empty, and whether the conversation stays in the interactive state.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and whether unauthorized content is invisible.
- Check the field names and required markers one by one in the node configuration, and confirm that they correspond one-to-one with the material fields of the three-stage review sheet, proof, and proofreading record.
- Reference the
formInputResultandselectResultfields in subsequent nodes and run a trial, confirming that the corresponding field values can be retrieved after submission.