What this category's data looks like
This category's data looks like this: Journal publication licenses and annual verification involve three types of materials: the journal publication license, the annual verification form, and the rectification report. License fields include name, publication number, competent and sponsoring units, validity period, and signature and seal; the annual verification form includes year, publication period, publication status, personnel and asset data; the rectification report includes issue items, rectification measures, completion date, and responsible person's signature. The material sources are daily publication records and special inspection conclusions, and the update cadence advances according to the annual verification cycle and rectification deadlines. When entering the workflow, the license serves as the subject qualification credential, the annual verification form serves as the periodic data summary, and the rectification report serves as the issue closed-loop explanation; the fields of the three must be cross-consistent, and dates and signatures must be traceable.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The "issuable material drafts and handover records" are continued and completed by subsequent nodes according to the branches. When the user selection node is triggered, the conversation enters the interaction 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 name, publication number, competent and sponsoring units, validity period, signature and seal are complete, and whether the version and date are consistent | Check the original license and registration records field by field, verify the options and branch connections one by one in the node, and confirm that the license information enters the corresponding branch |
| Annual verification form | Whether the year, publication period, publication status, personnel and asset data are consistent with the license and rectification report, and whether the date and signature are complete | Cross-compare the same record name, quantity, and date across the annual verification form, license, and rectification report, and trigger one check of the node status in the run records |
| Rectification report | Whether the issue items, rectification measures, completion date, responsible person's signature, and receipt are complete, and whether the version is synchronized | Check the issue items and dates of the rectification report and the annual verification form, reference the selection result variable in subsequent nodes, and run a test once |
| Handover record | Whether the responsible person, receipt time, version number, and receipt are clear, and whether the fields are complete | Draft one according to the template and complete one handover, check whether missing items are blocked, and confirm the branch direction and interaction state records |
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 drafted separately, without cross-field comparison and unified value selection.
- Symptom: The rectification report version is not synchronized, and the annual verification form still references the old version of the issue items. Cause: After the version update, re-verification was not triggered, and the handover record did not indicate the version number.
- Symptom: A signature or receipt is missing, and the material cannot enter the next step for signing acceptance. Cause: The responsible person did not confirm the branch in the node, and the handover record did not record the acceptance status.
How to verify the setup
How to verify the setup: Acceptance of this feature: run tests option by option, check the branch direction and interaction state in the run records, confirm that the options and branch connections are consistent, that the selection result variable has been passed to subsequent nodes, and verify the correspondence among variables, nodeId, and the options.
Business test: Draft one according to the template and complete one handover, and see whether missing items are blocked.
- In the node, verify the options and branch connections one by one, trigger one check of the node status in the run records, and confirm that the interaction state is recorded.
- Reference the selection result variable in subsequent nodes and run a test once, check
variablesandnodeId, and confirm that the branch direction is consistent with the interaction state records.