What this category's data looks like
In the scenario of annual progress and acceptance of research projects, materials enter in batches by three categories: annual progress reports, mid-term inspection materials, and acceptance reports. Annual progress reports are mostly submitted by the project team according to annual milestones, with fields concentrated on task completion, stage results, funding execution, and plans for the next year; mid-term inspection materials are collected by the management department in the middle of the project cycle, with fields emphasizing indicator achievement, personnel input, and adjustment explanations; acceptance reports are summarized at project closure, with fields covering all assessment indicators, a results list, and signature pages. The three types of materials have different sources and different update rhythms: progress reports roll over annually, mid-term materials are formed once, and acceptance reports no longer change after finalization. When entering the exception tracing and manual review workflow, annual progress reports play the role of process records, mid-term inspection materials play the role of comparison benchmarks, and acceptance reports play the role of conclusion basis, with fields, dates, and signatures referenced item by item between nodes.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "exception list and review conclusions" are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an 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 |
|---|---|---|
| Annual progress report | Whether the name, quantity, date, and signature page are consistent with the same record in the mid-term inspection materials | Extract record fields one by one, compare them side by side with the same-named fields in the mid-term inspection materials, write differences into the exception list, and annotate the source line |
| Mid-term inspection materials | Whether the version number and receipt are synchronized to the version referenced in the acceptance report | Check the material version identifier against the reference location in the acceptance report, and separately mark records missing signatures or receipts |
| Acceptance report | Whether the assessment indicators, results list, and signature column are complete and traceable | Trace back item by item through the annual progress reports and mid-term inspection materials according to the indicators, and confirm that each conclusion is supported by original records |
| User selection node | Whether each option corresponds to one branch, and whether the selection result variable is passed to subsequent nodes | Check the options and branch connections one by one in the node, reference variables in subsequent nodes and run a trial once, and inspect the nodeId status in the run records |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the annual progress report and the acceptance report. Cause: The two materials are entered separately by different nodes, and the fields have not undergone same-source comparison.
- Phenomenon: The version of the mid-term inspection materials is not synchronized, and the acceptance report still references old-version data. Cause: The version identifier is not passed along with material updates, and the reference location is not checked back.
- Phenomenon: Records missing signatures or receipts enter the review conclusions. Cause: The signature column and receipt are not used as pre-checks for entering the branch.
How to verify the setup
Acceptance of this function: run trials option by option, check the branch directions and interaction states in the run records, and confirm that each option corresponds to one branch, the selection result variable has been passed to subsequent nodes, and the same session does not repeatedly enter interaction.
Business test: create an exception record, see whether the source material can be traced, and check whether the exception list and review conclusions have original record support and reviewer signatures.
- In the user selection node, check the options and branch connections one by one, and confirm that each option corresponds to one branch.
- Reference
variablesin subsequent nodes and run a trial once, and inspect thenodeIdstatus and branch directions in the run records.