What this category's data looks like
In the journal publication license and annual verification scenario, three types of materials enter the workflow at the same time: the journal publication license, the annual verification form, and the rectification report. The license carries the entity name, publication number, validity period, and issuance date; the annual verification form carries the annual verification conclusion, verification date, and handler signature; the rectification report carries issue items, rectification completion date, and review signature. The three types of materials come from different sources and have different update rhythms: the license is reissued upon changes, the annual verification form is generated in batches by year, and the rectification report is filled back item by item by issue. In terms of field characteristics, the four types of fields—name, quantity, date, and signature—are most prone to variant spellings of the same item. When entering this feature, the license serves as the baseline identity material, the annual verification form serves as the annual conclusion material, and the rectification report serves as the issue closure material; the three need to establish a traceable correspondence in the same exception list.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "exception list and review conclusion" is then completed by subsequent nodes continuing execution according to the branch. When a node is triggered, the conversation enters an interactive state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | Compare the entity name, publication number, validity period, and issuance date item by item against the corresponding fields in the annual verification form and rectification report | Retrieve the original scanned copy of the license, check whether the name and publication number are consistent with the other two materials, and record the differing fields and the page numbers where they appear |
| Annual verification form | Check whether the verification year, verification conclusion, verification date, and handler signature form a closed chain with the dates and signatures in the license and rectification report | Retrieve the verification form by year, compare whether the verification date falls within the license validity period, and check whether the handler signature and receipt are complete |
| Rectification report | Check whether the issue items, rectification completion date, and review signature correspond one-to-one with the issues listed in the annual verification form | Extract rectification items one by one, trace back to the issue number and completion date in the source materials, and check whether the review signature matches the signer on the verification form |
| Exception record | Check whether the original record support, reviewer signature, branch direction, and interaction state records are traceable | In the node, check the options and branch connections one by one, reference variables and nodeId to locate the run record, and confirm that the selection result variable has been passed to subsequent nodes |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the license and the annual verification form. Cause: The two materials were entered separately, no field-level comparison was made against the original record as the baseline, and differences were not flagged.
- Symptom: The rectification report has been updated, but the annual verification form still references the old version of the issue items. Cause: The versions were not synchronized, updating the material did not trigger re-verification, and the old version content continued to participate in conclusion generation.
- Symptom: The exception list lacks a review signature or receipt. Cause: The signature and receipt steps were not included in the verification actions, and although the exception record has original record support, the reviewer cannot be confirmed.
How to verify the setup
Feature acceptance: run through each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes, and use variables and nodeId to locate the state record.
Business test: create an exception record, see whether it can be traced back to the source material, check whether the exception list and review conclusion have original record support and a reviewer signature, and then hand it over to the person in charge for handling.
- In the node, check the options and branch connections one by one, trigger it once, then view the node status in the run record to confirm that the default branch was not taken and that the process did not stop.
- Reference the selection result variable in a subsequent node and run it once, then check that the branch direction and interaction state records pointed to by
variablesandnodeIdare consistent.