What this category's data looks like
In the scenario of scientific research project task book signing, the category materials that enter the deployment, operations, and application handover stage include the project task book, the project task breakdown table, and the budget book. The project task book comes from the formal text finalized after project approval, and its update cadence is triggered by project adjustments or supplementary agreements; its fields include project name, undertaking unit, start and end dates, total funding, signatures, and receipts. The project task breakdown table comes from splitting the task book, and updates change with the addition or removal of subprojects; its fields include subproject name, responsible person, delivery milestones, and quantity basis. The budget book comes from funding approval, and updates change with budget adjustments; its fields include subject, amount, date, and approval signature. When the three enter workflow orchestration, the task book serves as the main record anchor, the breakdown table serves as the basis for node expansion, and the budget book serves as the source of branch conditions, each playing a different role.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "Handover-ready deployment status and operation records" are completed by subsequent nodes continuing execution 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 |
|---|---|---|
| Project task book | Whether the project name, start and end dates, signatures, and receipts are complete | Check the fields item by item against the original task book, check whether the signature page and receipt have missing items, and record the date basis |
| Project task breakdown table | Whether the subproject names, responsible persons, and delivery milestones are consistent with the task book | Compare the names and dates in the breakdown table and the task book row by row, and check whether the variables references point to the same record |
| Budget book | Whether the subjects, amounts, dates, and approval signatures match the task book | Check the amounts and dates item by item by subject, check the approval signatures and receipts, and mark items whose versions are not synchronized |
| Workflow node | Whether the options and branch connections correspond one to one, and whether the interaction state is recorded | Check the options and branch connections one by one in the node, trigger it once, and view the node status and nodeId in the run record |
Three common errors
- Symptom: The name, quantity, and date of the same project do not match across the two materials. Cause: The task book and the breakdown table were revised separately, without field-level comparison and version synchronization.
- Symptom: The amount in the budget book is inconsistent with the total funding in the task book. Cause: After the budget adjustment, the task book was not written back, the versions were not synchronized, and signatures and receipts are missing.
- Symptom: After selecting an option, the default branch is still taken. Cause: The options and branch connections were not checked one by one, and the selection result variable was not correctly passed to subsequent nodes.
How to verify the setup
Acceptance of this feature: test-run each option one by one, check the branch direction and interaction state in the run record, confirm that the selection result variable has been passed to subsequent nodes, and check that the variables and nodeId references are consistent.
Business test: check the handover form item by item once, see which record is missing, and focus on checking whether the fields, dates, and signatures of the task book, breakdown table, and budget book are consistent across all three.
- Check the options and branch connections one by one in the node, trigger it once, and view the node status and
nodeIdin the run record - Compare the names, quantities, dates, and signature receipts of the task book, breakdown table, and budget book item by item by subject and project, and mark items whose versions are not synchronized