What this category's data looks like
This category's data looks like Annual progress and acceptance of scientific research projects involve three types of materials: annual progress reports, mid-term inspection materials, and acceptance reports. Annual progress reports are updated at quarterly or annual milestones, with fields including task name, planned progress, actual completed amount, funding expenditure, and signature of the person in charge; mid-term inspection materials are submitted in the middle of the project cycle, with fields including phase objectives, indicator completion status, equipment purchase list, expert opinions, and receipts; acceptance reports are formed at project closure, with fields including results list, assessment indicator comparison, audit data, acceptance conclusions, and multi-party signatures. When the three types of materials enter workflow orchestration, their roles differ: annual progress reports serve as process records that trigger node transitions, mid-term inspection materials serve as phase evidence for branch decisions, and acceptance reports serve as the final-state basis for handover archiving. Material sources are project management system exports and offline signed scans, the update rhythm is synchronized with project milestones, and field characteristics require that names, quantities, and dates remain consistent across materials.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The handover-ready deployment state and operation records are continued and completed by subsequent nodes according to the branches. 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 | Fields include task name, planned progress, actual completed amount, funding expenditure, and signature of the person in charge; dates must be consistent with project milestones | Check the task names in the report against the mid-term inspection materials and acceptance report item by item, and check whether the signature fields and receipts are complete |
| Mid-term inspection materials | Fields include phase objectives, indicator completion status, equipment purchase list, expert opinions, and receipts; quantities and dates must be consistent across materials | Compare the quantities in the equipment purchase list with the annual progress report and acceptance report, and confirm that versions are synchronized and that expert signatures and receipts are not missing |
| Acceptance report | Fields include results list, assessment indicator comparison, audit data, acceptance conclusions, and multi-party signatures; names and dates must match earlier materials | Check the names and dates in the results list against the annual progress report and mid-term inspection materials item by item, and check whether multi-party signatures and audit receipts are complete |
| User selection node | Each option corresponds to one branch, and variables records the selection result and passes it to subsequent nodes | Check the options and branch connections one by one in the node, trigger it once, and view the node status and branch direction in the run records |
Three common errors
- Symptom: The names, quantities, and dates of the same record do not match between the annual progress report and the acceptance report. Cause: The two materials were filled in by different personnel, and no cross-material field comparison was performed.
- Symptom: The mid-term inspection materials and the acceptance report are not synchronized in version, and differences appear in the equipment list quantities. Cause: After the materials were updated, they were not uniformly written back, and the old version was still in circulation.
- Symptom: The acceptance report lacks signatures or receipts, and items are missing when checking the handover form item by item. Cause: The signature process was not closed-loop, and receipts were not archived to the corresponding node records.
How to verify the setup
Acceptance of this feature: trial-run each option one by one, check the branch direction and interaction state in the run records, and confirm that variables has been passed to subsequent nodes and that the node record is located by nodeId.
Business test: check once item by item according to the handover form, see which record is missing, and confirm that version, connection, and task record are consistent.
- In the user selection node, check the options and branch connections one by one, trigger it once, and view the node status and branch direction in the run records.
- Reference the selection result variable in a subsequent node and trial-run it once to confirm that the records corresponding to
variablesandnodeIdare complete.