What this category's data looks like
Annual progress and acceptance of research projects involve three types of materials: annual progress reports, mid-term inspection materials, and acceptance reports. The sources are project team submissions at milestones, management department archiving, and review records. The update cadence rolls with the inspection cycle, and the field characteristics center on name, quantity, date, signature, and receipt. Annual progress reports focus on phased tasks and indicator completion, mid-term inspection materials focus on milestone objectives and funding execution, and acceptance reports focus on final results and conclusions. When the three types of materials enter the workflow, the annual progress report serves as the comparison baseline, the mid-term inspection materials serve as process verification, and the acceptance report serves as final-state confirmation. The name, quantity, and date of the same record must remain consistent across any two of them, signatures and receipts must be complete, and versions must be synchronized.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The discrepancy list is completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interactive 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 |
|---|---|---|
| Annual progress report | The name, quantity, and date of the same record are consistent with the ledger, and signatures and receipts are complete | Check the options and branch connections one by one in the node, and reference variables to see whether the selection result variable is passed to subsequent nodes |
| Mid-term inspection materials | They match the name, quantity, and date of the annual progress report, and the version is synchronized | Trigger an interaction once, check the node status in the run record, and verify the branch direction corresponding to nodeId |
| Acceptance report | It is consistent with the name, quantity, and date of the mid-term inspection materials; missing signatures or receipts must be flagged | Reference the selection result variable in a subsequent node and run a trial once, and verify the correspondence between variables and nodeId |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match across two materials. Cause: The reporting standards are not unified, field sources are not synchronized, and the same object is not locked during comparison.
- Symptom: The version is not synchronized, and old-version materials are still referenced. Cause: After materials are updated, the ledger is not written back, and the workflow branch still points to the old-version record.
- Symptom: Signatures or receipts are missing, and the acceptance conclusion cannot be closed. Cause: The signature page and receipt were not archived together with the materials, and the process stopped after the interaction was completed instead of continuing.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch direction and interaction state in the run record, and confirm that variables and nodeId can be referenced in subsequent nodes.
Business test: use one real record to find fields inconsistent with the ledger, and hand them to the reviewer for confirmation and write-back.
- Check the options and branch connections one by one in the node, and trigger one run to view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once, and verify the correspondence between
variablesandnodeId.