What this category's data looks like
This page focuses on journal publication license and annual verification materials, covering three types of materials: journal publication licenses, annual verification forms, and rectification reports. The sources are license issuance records, annual submission receipts, and rectification feedback receipts, and the update cadence advances with the verification cycle and rectification milestones. The three types of materials play different roles when entering the workflow: the journal publication license serves as the qualification basis for authorized access, the annual verification form serves as the reference basis for the scope of external services and annual status, and the rectification report serves as the trigger material for narrowing or restoring the authorization scope. Field characteristics are concentrated in names, quantities, dates, and signature receipts, and the consistency of the same record across different materials must be compared item by item.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. "Externally available entry points and authorization scope" are completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interactive state and the workflow status is recorded. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | The qualification basis for authorized access and the permitted scope of external service entry points | Check the options and branch connections one by one in the node, and confirm that the license fields, dates, and signature receipts are consistent with the annual verification form |
| Annual verification form | The reference basis for the scope of external services and annual status | Trigger a user selection node once, check the node status in the run records, and verify that the verification form's name, quantity, and date are consistent with the license |
| Rectification report | The trigger material for narrowing or restoring the authorization scope | Reference the selection result variable in a subsequent node and run a trial once, checking whether the rectification report's signature and receipt are complete and whether the version is synchronized |
| User selection node | Options correspond one-to-one with branches, and the interaction status is recorded | Run a trial for each option one by one, check the branch direction and interaction status in the run records, and confirm that the selection result variable has been passed to subsequent nodes |
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, lacking cross-material field comparison and receipt verification.
- Symptom: The rectification report version is not synchronized, and the authorization scope still provides external services according to the old version. Cause: The version update did not trigger the user selection node to re-run the branch.
- Symptom: The annual verification form lacks a signature or receipt, but the external entry point remains open. Cause: After the interaction is completed, the process stops, and subsequent nodes do not continue execution according to the branch.
How to verify the setup
This feature acceptance: Run a trial for each option one by one, check the branch direction and interaction status in the run records, confirm that the selection result variable has been passed to subsequent nodes, and verify that variables and nodeId are queryable in the records.
Business test: Access once with a restricted identity and see whether the visible scope matches the settings.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference the selection result variable in a subsequent node and run a trial once, and verify the passing results of
variablesandnodeId.