What this category's data looks like
This category's data involves three types of materials: the journal publication license, the annual verification form, and the rectification report. The license fields include journal name, journal number, competent and sponsoring units, validity period, and issuance date, with the signature field being the legal representative; the annual verification form fields include journal name, journal number, year, publication status, personnel, and assets, and requires dual signatures from the sponsoring unit and the publishing unit; the rectification report fields include issue items, rectification measures, completion date, and acceptance signature. The material sources are license issuance records, annual submissions, and rectification receipts, and the update cadence is license renewal upon expiration, centralized annual verification, and time-limited rectification submissions. When entering workflow orchestration, the license serves as the main record anchor, the annual verification form serves as the annual comparison source, and the rectification report serves as the supplement for discrepancies and receipts; the three are aligned by journal name and journal number before participating in branch decisions.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "Handover-ready deployment status and operation records" are then completed by subsequent nodes continuing execution along the branches. When a node is triggered, the conversation enters an interaction 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 |
|---|---|---|
| Journal publication license | Whether the journal name, journal number, competent and sponsoring units, validity period, and issuance date are consistent with the annual verification form, and whether the signature field is complete | Check the options and branch connections one by one in the node, compare the journal name, journal number, and date fields of the license and the annual verification form, and mark as pending supplementation if a signature is missing |
| Annual verification form | Whether the year, publication status, personnel, and assets correspond to the license and the rectification report, and whether the dual signatures of the sponsoring unit and the publishing unit are complete | Trigger a user selection node once, check the node status in the run records, and verify whether the number of issue items and dates in the annual verification form and the rectification report match |
| Rectification report | Whether the issue items, rectification measures, completion date, and acceptance signature correspond one-to-one with the issues listed in the annual verification form, and whether the receipts are all attached | Reference variables in a subsequent node and run a trial once, verify the item names, quantities, and dates of the rectification report and the annual verification form, and return to the interaction state if a receipt is missing |
| Workflow node | Whether the options and branches correspond one-to-one, whether the interaction state is recorded, and whether the selection result variable has been passed to subsequent nodes | Check the options and branch connections in the node, trigger once to view the nodeId and node status in the run records, and reference variables in a subsequent node for a trial run |
Three common errors
- Symptom: The name, quantity, and date of the same journal do not match across the two materials. Cause: The license and the annual verification form are maintained separately, and alignment by journal name and journal number is not completed before entering branch decisions.
- Symptom: Versions are not synchronized, and the annual verification form still references the old journal number after license renewal. Cause: The material update cadences differ, and version comparison and replacement are not completed before the node is triggered.
- Symptom: The rectification report lacks a signature or receipt, but the annual verification form has already been marked complete. Cause: The receipt does not enter the interaction state together with the rectification report, and the branch direction is disconnected from the actual material status.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch directions and interaction states in the run records, confirm that options and branch connections correspond one-to-one, that the selection result variable has been passed to subsequent nodes, and that both nodeId and variables are traceable.
Business testing: check item by item once according to the handover sheet, see which record is missing, and focus on checking whether the fields, dates, and signatures of the license, annual verification form, and rectification report are complete.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and trigger once to view the node status in the run records.
- Reference
variablesin a subsequent node and run a trial once, verify whether the selection result variable has been passed, and also check whether the interaction state record corresponding tonodeIdis complete.