What this category's data looks like
Annual progress and acceptance of research projects involve three types of materials: annual progress reports, mid-term review materials, and acceptance reports. Annual progress reports are submitted at annual milestones, focusing on task completion and fund usage; mid-term review materials are used for periodic assessment, including indicator comparisons and adjustment notes; acceptance reports summarize results, tests, and signatures at project closure. Material sources include project team submissions, countersignatures from collaborating units, and receipts from management departments, with an update cadence that rolls with the milestones. In multilingual materials and terminology handling, the three types of materials each play different roles: annual progress reports provide process data, mid-term review materials provide indicator baselines, and acceptance reports provide final conclusions. Field characteristics center on record names, quantities, dates, signatures, and receipts; the same record often exhibits differences in wording, values, and versions across the three materials.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "unified terminology glossary and comparison draft" is continued and completed by subsequent nodes according to the branch. 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 chosen option.
| Object | Check | Verification action |
|---|---|---|
| Annual progress report | Whether the same record's name, quantity, and date match those in the mid-term review materials and acceptance report | Check the options and branch connections one by one in the node, trigger it once to view the node status in the run records, and reference the selection result variable in a subsequent node for a trial run |
| Mid-term review materials | Whether the indicator comparisons and adjustment notes are version-synchronized with the annual progress report and acceptance report | Check the record names, quantities, and dates within the materials, inspect the version numbers and receipts, and confirm the branch direction and interaction state records |
| Acceptance report | Whether signatures and receipts are complete, and whether the conclusions are consistent with the annual progress report and mid-term review materials | Reference variables and nodeId in subsequent nodes, and after a trial run check the branch direction and interaction state records |
| Multilingual terminology glossary and comparison draft | Whether the same term is written consistently throughout, and whether the translated name can refer back to the source text | Sample three terms to check their wording throughout, and verify the variables passing and nodeId records |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the annual progress report and the acceptance report. Cause: The materials are filled in separately, without cross-material field comparison and unification.
- Symptom: The mid-term review materials and the acceptance report are not version-synchronized, and old-version data is still referenced. Cause: After a version update, re-verification and branch confirmation were not triggered.
- Symptom: The acceptance report lacks signatures or receipts, yet the process has already continued. Cause: After the interaction was completed, the branch direction and interaction state records were not checked, and the receipt check was missed.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch directions and interaction states in the run records, and confirm that the selection result variable has been passed to subsequent nodes.
Business test: sample three terms to check whether their wording is consistent throughout, and verify whether the translated names can refer back to the source text.
- Check the options and branch connections one by one in the node, and trigger it once to view the node status in the run records.
- Reference
variablesandnodeIdin subsequent nodes and perform a trial run, then check the branch direction and interaction state records.