What this category's data looks like
The signing of research project task books involves three types of materials: the project task book, the topic task breakdown table, and the budget book. The task book comes from the project application system and is locked upon signing; the breakdown table is decomposed by the topic leader according to the task book and updated with personnel adjustments; the budget book is prepared by subject and finalized after financial review. Field characteristics center on names, quantities, dates, and signatures: the topic names, number of participants, and start/end dates of the task book and the breakdown table must be consistent; the budget book amounts correspond to the funding column of the task book; signatures and receipts are indispensable. When materials enter workflow orchestration, the task book serves as the main record, the breakdown table as sub-items, and the budget book as an attachment; together, the three determine the scope of authorized access and the entry point for external services.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "External entry points and authorization scope" 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 |
|---|---|---|
| Project task book | Whether the name, quantity, date, and signature are consistent with the breakdown table | Check the options and branch connections one by one in the node, trigger once, and view the node status in the run record |
| Topic task breakdown table | Whether the version is synchronized, and whether the sub-item names match the main record of the task book | Reference the selection result variable in a subsequent node and run a trial once to check whether the variable has been passed to the subsequent node |
| Budget book | Whether the amounts and subjects are consistent with the funding column of the task book, and whether the receipts are complete | Access once with a restricted identity to check whether the visible scope matches the visitor's identity and authorization scope |
| User selection node | Each option corresponds to one branch; whether the branch direction and interaction state are recorded | Check the options and branch connections one by one in the node, and check whether the variables and nodeId references are correct |
Three common errors
- Symptom: The name, quantity, and date of the same topic do not match across the two materials. Cause: The breakdown table was decomposed according to an old version of the task book, and was not updated synchronously after the task book was signed.
- Symptom: The budget book amount is inconsistent with the funding column of the task book. Cause: The budget book version was not synchronized, and the financial review draft and the final signed draft were mixed up.
- Symptom: Signatures or receipts are missing, but the external service entry point has already been opened. Cause: The authorization scope was released before signatures and receipts were complete, and the visitor's identity did not match the visible scope.
How to verify the setup
Acceptance of this feature: Run a trial for each option one by one, check the branch direction and interaction state in the run record, and confirm that variables, nodeId, and the selection result variable references are correct.
Business test: Access once with a restricted identity and see whether the visible scope matches the settings.
- Check the options and branch connections one by one in the node, trigger once, and view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that it has been passed to the subsequent node.