What this category's data looks like
The materials in the signing stage of scientific research project task books mainly consist of the project task book, the subject task breakdown table, and the budget book. Their sources are exports from the application system, scanned copies stamped by the lead organization, and receipts from the subject undertaking parties. The update cadence follows the signing rounds: the first draft, the joint-signature draft, and the stamped final version each form a version, with fields concentrated in names, quantities, dates, amounts, and signature positions. When entering workflow orchestration, the project task book plays the role of the main record, the subject task breakdown table plays the role of splitting and responsibility correspondence, and the budget book plays the role of funding basis and budget subjects. The three serve as mutual comparison baselines. If any field deviates between two materials, it enters the scope of exception tracing and is confirmed by manual review.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "exception list and review conclusions" are completed by subsequent nodes continuing execution according to the branches. When a node is triggered, the conversation enters an interactive state and records the workflow status. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Project task book | Check whether the name, quantity, date, and signature position are consistent with the subject task breakdown table | Compare the two materials field by field, record the locations of differences, and view in the run record the branch direction corresponding to nodeId |
| Subject task breakdown table | Check whether the split subject names, undertaking parties, and start and end dates are consistent with the budget book basis | Compare the split entries with the budget subjects, and reference the selection result variable in variables to run a trial once |
| Budget book | Check whether the subject amounts, quantities, and stamped receipts are complete, and whether the versions are synchronized | Check the stamped pages and receipts, and confirm that entries missing signatures or receipts enter the exception list |
| Exception list and review conclusions | Check whether each exception is supported by original records and whether the reviewer has signed | Trace each item back to the source material page number and version number, and return unsigned items for supplementation |
Three common errors
- Phenomenon: the same subject name is written differently in the task book and the breakdown table. Cause: the two materials are filled in by different roles, and no unified field mapping has been made.
- Phenomenon: the budget book amount has been adjusted, but the task book is still the old version. Cause: the versions are not synchronized, and the update cadence has not been aligned with the signing rounds.
- Phenomenon: exception items lack signatures or receipts. Cause: the review step leaves no trace, and the manual review conclusions have not been backfilled into the list.
How to verify the setup
In the nodes, check the options and branch connections one by one, and confirm that each option corresponds to one branch.
Trigger an interaction once, and view the node status and variables values in the run record.
- This feature acceptance: run trials option by option, check the branch directions and interaction status in the run record, and confirm that the selection result variable has been passed to subsequent nodes.
- Business test: create an exception record and see whether it can be traced back to the source material.