What this category's data looks like
During the signing stage of a research project task book, the materials mainly consist of the three-piece set: the project task book, the subject task breakdown table, and the budget book. The sources are the export draft from the application system, the draft filled in by the subject leader, and the draft verified by finance. The update rhythm is concentrated in multiple rounds of revision before signing and change filing after signing. Field characteristics include subject name, leader, start and end dates, funding categories, amounts, and signature and receipt columns. When entering this function, the project task book serves as the main record carrying the overall objectives and assessment indicators, the subject task breakdown table provides the sub-project names, quantities, and dates, and the budget book provides the funding categories and amounts. Together, the three form the comparison draft for the version ledger and change records, providing the material basis for subsequent branches to continue execution.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The version ledger and change records are completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters the interaction 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 | Whether the subject name, leader, start and end dates, and signature and receipt columns are consistent with the breakdown table | Check the options and branch connections one by one in the node, use nodeId to locate the node, and after a trial run check the node status in the run record |
| Subject task breakdown table | Whether the sub-project names, quantities, and dates match the task book and budget book | Reference variables in subsequent nodes and run once to confirm that the selection result variable has been passed to subsequent nodes |
| Budget book | Whether the funding categories, amounts, dates, and signatures are consistent with the task book | Trigger one interaction, check the node status in the run record, and confirm that the branch direction is correct after entering the interaction state |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, check whether the version number and references are updated synchronously, and check whether the old version is traceable |
Three common errors
- Symptom: The name, quantity, and date of the same subject do not match across two materials. Cause: The filled-in draft did not unify the standards, and field-level comparison was not performed before signing.
- Symptom: The version is not synchronized, and the old version is still referenced. Cause: The ledger was not updated after the change, and subsequent nodes still continue execution according to the old branch.
- Symptom: Signatures or receipts are missing, and the materials are incomplete. Cause: The signing process was not completed, and the interaction status was not recorded in the run record.
How to verify the setup
This function's acceptance: run each option one by one, check the branch direction and interaction status in the run record, and confirm that the option corresponding to nodeId and the branch connection are correct.
Business test: change one piece of content, see whether the version number and references are updated synchronously, and check whether variables take effect in subsequent nodes.
- Check the options and branch connections one by one in the node, and after a trial run check the node status and branch direction in the run record.
- Reference
variablesin subsequent nodes and run once to confirm that the selection result variable has been passed in and the version ledger references are synchronized.