What this category's data looks like
This page centers on journal publication licenses and annual verification, bringing three types of materials—journal publication licenses, annual verification forms, and rectification reports—into a single workflow. The license provides the journal name, publication number, sponsoring organization, validity period, and issue date; the annual verification form records the verification year, submission date, signature, and receipt; the rectification report carries the issue items, rectification deadline, and completion status. Materials are updated on a rolling weekly or monthly basis, and the fields are mainly names, quantities, dates, and signatures. When entering this feature, the license serves as the baseline object, the verification form as the periodic object, and the rectification report as the exception object; each of the three assumes a verification role, with workflow nodes recording the branch direction, and subsequent nodes then summarizing them into a progress table and a statement of statistical criteria.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "progress table and statement of statistical criteria" is 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 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 fields, dates, and signatures are consistent with the annual verification form | In the node, check the options and branch connections one by one, reference variables and nodeId, and trigger once to view the node status in the run records |
| Annual verification form | Whether the name, quantity, and date of the same record match across the two materials | In subsequent nodes, reference the selection result variable and run a trial once, and check whether the journal name, publication number, and year are consistent between the annual verification form and the license |
| Rectification report | Whether the version is synchronized, and whether missing signatures or receipts have been completed | In the node, check the options and branch connections one by one, trigger once to view the node status in the run records, and check the rectification items and receipt signature |
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 are maintained separately, and verification was not backfilled using the same baseline fields.
- Symptom: The rectification report version is not synchronized, and old entries remain in the progress table. Cause: After the materials were updated, the workflow was not re-entered, and the branch direction continued to execute according to the old records.
- Symptom: The annual verification form lacks a signature or receipt, and the rectification report lacks confirmation of rectification completion. Cause: After the interaction is completed, the process stops, and the signature and receipt fields are not completed in subsequent nodes.
How to verify the setup
Feature acceptance: Run trials option by option, check the branch directions and interaction status in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and verify the references to variables and nodeId.
Business testing: Use one week of records to check the totals, see whether the criteria and exceptions are clearly stated, confirm that the record count matches the statistical count, and that the criteria are written in the table header.
- In the node, check the options and branch connections one by one, trigger once to view the node status in the run records, and confirm that the interaction status is recorded.
- In subsequent nodes, reference the selection result variable and run a trial once, check the branch direction and interaction status records, and confirm that the process has not stopped.