What this category's data looks like
Journal publication license and annual verification materials mainly come from three types: the journal publication license, the annual verification form, and the rectification report. The license records the journal name, journal number, sponsoring unit, publishing unit, validity period, and issuance date; its field structure is fixed, and its update rhythm is marked by license renewal and change registration. The annual verification form is filed annually and contains the journal name, journal number, publishing unit, verification year, signature, and receipt, accumulating period by period. The rectification report is generated along with verification opinions and contains issue items, rectification measures, completion date, and signature; its update rhythm depends on the rectification cycle. After the three types of materials enter the workflow, their roles differ: the license serves as the baseline object, the verification form serves as the object to be compared, and the rectification report serves as the supplementary explanatory object. The three verification dimensions of fields, dates, and signatures are expanded item by item within the nodes.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "discrepancy list" is completed by subsequent nodes continuing execution according to 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, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | Whether the fields, dates, and signatures are consistent with the ledger | Check the options and branch connections one by one in the user selection node, and reference variables to record the journal name, journal number, and validity period; view the node status in the run records to confirm that the interaction state is recorded |
| Annual verification form | Whether the name, quantity, and date of the same record match between the license and the verification form | Reference the selection result variable in subsequent nodes and run a trial once, comparing the verification year, publishing unit, signature, and receipt; use nodeId to locate the node and check the branch direction |
| Rectification report | Whether the version is synchronized and whether signatures or receipts are complete | Check the rectification items, completion date, and signature one by one in the node; trigger an interaction once and view the node status and branch direction corresponding to nodeId in the run records |
| Discrepancy list | Whether inconsistent fields are located to the specific object and row | Continue execution according to the branch and write back the discrepancy list; reference the selection result variable in variables to confirm that the process continues downward after the interaction is completed |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the license and the verification form. Cause: The two materials have different filing standards, and no item-by-item comparison was performed within the node.
- Symptom: The rectification report version is not synchronized, and old-version items remain in the list. Cause: After the material was updated, the interaction was not retriggered, and the branch still followed the old path.
- Symptom: The verification form lacks a signature or receipt, but the list is still judged as consistent. Cause: Signatures and receipts were not included in the verification dimensions, and the node did not record the interaction state.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, and that the selection result variable has been passed to subsequent nodes.
Business test: use a real record to find fields inconsistent with the ledger, locate the specific row in the license, verification form, or rectification report, and submit it to the reviewer for confirmation and write-back.
- Check the options and branch connections one by one in the user selection node, trigger an interaction once, and view the node status and branch direction in the run records.
- Reference the selection result variable in subsequent nodes and run a trial once to confirm that the process continues downward after the interaction is completed, and that the discrepancy list is written back according to the branch.