What this category's data looks like
Journal publishing license and annual verification materials include the journal publishing license, annual verification form, and rectification report. Sources are approval replies from the licensing authority, submissions by the sponsoring organization, and rectification receipts. The update cadence advances with license changes, annual verification cycles, and rectification deadlines. Field characteristics center on names, quantities, dates, and signatures: the license states the journal name, journal number, and validity period; the annual verification form states the year, publication period, and verification conclusion; the rectification report states the issues, measures, and approval signature. When the materials enter workflow orchestration, the license and verification form serve as version baselines, and the rectification report serves as the change trigger item; together, the three support the version ledger and change records.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The "version ledger and change records" are continued and completed by subsequent nodes according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Journal publishing license | Whether the fields, dates, and signatures are consistent with the annual verification form | Compare the journal name, journal number, validity period, and approval date item by item, and use variables to record differences |
| Annual verification form | Whether the name, quantity, and date of the same record match the license | Check the publication period, quantity, and conclusion column by column by year, locate the node with nodeId, and then run a trial |
| Rectification report | Whether the signatures or receipts are complete and whether the version is synchronized | Check the approval signature and receipt, and confirm that the current version is unique and the old version is traceable |
| Version ledger and change records | Whether references are updated synchronously with the version number | After changing one piece of content, check the ledger version number and external document references |
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 were filled out separately and were not checked against the same field baseline.
- Symptom: The rectification report has been updated, but the ledger and external documents still reference the old version. Cause: The version was not synchronized, and references were not linked to the version number.
- Symptom: The verification form lacks a signature or the rectification report lacks a receipt. Cause: The approval step was not closed-loop, and the materials were not archived according to node status.
How to verify the setup
Acceptance for this feature: run trials option by option, check the branch directions and interaction states in the run records, and confirm that options correspond one-to-one with branches and that the selection result variable has been passed to subsequent nodes.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- In the node, check the options and branch connections one by one, and use
variablesto confirm the selection result variable. - Trigger one interaction, view the node status in the run records, and use
nodeIdto locate it and then run a trial.