What this category's data looks like
This page focuses on the category of journal publication licenses and annual verification, involving three types of materials: journal publication license, annual verification form, and rectification report. License and verification materials are usually submitted by the reporting unit at the annual node, and the update cadence is synchronized with the verification cycle; the rectification report, on the other hand, circulates separately along with the rectification matter. The three types of materials play different roles when entering the intake stage: the license establishes the entity and scope, the verification form carries the annual data and signatures, and the rectification report corresponds to issue closure. Field characteristics are concentrated in names, quantities, dates, and signature receipts; the same record needs to be aligned item by item across multiple materials, and version desynchronization or missing signatures/seals often occur, so intake records and follow-up questions for completion need to first identify missing items before asking further.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "intake records and follow-up questions for completion" are continued and completed by subsequent nodes according to the branch. 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, quantity, date, and signature are consistent with the annual verification form | Check the options and branch connections one by one in the node, reference variables to read the license fields, and compare them with the records of the same name in the verification form |
| Annual verification form | Whether the name, quantity, and date of the same record match the license and the rectification report | Trigger once, check the node status in the run record, use nodeId to locate the node where the verification form is and check the fields |
| Rectification report | Whether signatures or receipts are missing, and whether the version is synchronized with the verification form | Reference the selection result variable in a subsequent node and run a trial once, and check the signature and receipt fields of the rectification report |
| Intake records and follow-up questions for completion | Whether missing items are identified and followed up on, and whether the answers are based on materials | Check according to the branch direction whether the follow-up questions cover the missing fields, and check the source of the material basis |
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 are filled in separately, and intake proceeds without field-level comparison.
- Symptom: The rectification report version is not synchronized and still references old-version verification form data. Cause: The materials have different update cadences, and the version identifier is not checked at intake.
- Symptom: Signatures or receipts are missing, and follow-up is not triggered. Cause: Missing-item identification does not cover signature/seal fields, and the branch direction does not enter the follow-up path.
How to verify the setup
Feature acceptance: run trials option by option, check the branch direction and interaction state in the run record, and confirm that variables, nodeId, and the selection result variable are all passed as expected.
Business test: submit a question missing key information and see whether it asks follow-up questions before answering.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger the user selection node once, and check the node status and interaction state record in the run record.