What this category's data looks like
Materials in the research funding budget adjustment and reimbursement category come from three routes: budget adjustment applications, reimbursement forms, and contract invoices. Budget adjustment applications record the adjusted account, amount, date, and approval signature; reimbursement forms record the expense name, quantity, date, handler, and approval signature; contract invoices record the contract number, invoice number, amount, invoice date, and seals from both parties. The update cadence varies with project phases and financial cycles: adjustment applications are submitted before budget execution, reimbursement forms are filled in after expenses occur, and contract invoices are collected at settlement. When materials enter workflow orchestration, budget adjustment applications serve as the starting point for branch decisions, reimbursement forms serve as the basis for execution at subsequent nodes, and contract invoices serve as evidence for verifying receipts and signature completeness. Field characteristics are concentrated in four categories: name, quantity, date, and signature. The same record must remain consistent across the three materials, and the version must be synchronized to the current node.
Configuration and implementation checks
This part is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Handover-ready deployment status and operation records" are completed by subsequent nodes continuing execution along 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 |
|---|---|---|
| Budget adjustment application | Check whether the adjusted account, amount, date, and approval signature are consistent with the contract invoice | Check the options and branch connections one by one in the node, and confirm that the name, quantity, and date match when the adjustment application serves as the starting point for branch decisions |
| Reimbursement form | Check whether the expense name, quantity, date, handler, and approval signature are consistent with the budget adjustment application | Reference the selection result variable in a subsequent node and run a trial once, and check whether the reimbursement form fields are correctly passed along the branch direction |
| Contract invoice | Check whether the contract number, invoice number, amount, invoice date, and seals from both parties are consistent with the reimbursement form | Trigger an interaction state once, check the node status in the run record, and confirm that the contract invoice, as receipt evidence, has no missing signature or receipt |
| Workflow node | Check whether 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, and check whether variables, nodeId, and the selection result variable have been passed to subsequent nodes |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the budget adjustment application and the reimbursement form. Cause: When materials enter the node, fields were not checked item by item according to the branch direction, and the version was not synchronized to the current node.
- Symptom: The contract invoice lacks a signature or receipt, and the approval signatures on the reimbursement form and budget adjustment application are incomplete. Cause: After the interaction is completed, the process stops, and subsequent nodes do not continue execution along the branch to check signatures and receipts.
- Symptom: After selecting an option, the default branch is still followed, and the same session repeatedly enters the interaction. Cause: The selection result variable is not correctly passed to subsequent nodes, and the references for
variablesandnodeIdare inconsistent.
How to verify the setup
Feature acceptance: 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 are correctly referenced in subsequent nodes.
Business testing: Check item by item once according to the handover form, see which record is missing, and confirm that the name, quantity, date, and signature of the budget adjustment application, reimbursement form, and contract invoice are consistent across all three.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and trigger once to view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once, and check whether the name, quantity, date, and signature of the budget adjustment application, reimbursement form, and contract invoice are consistent.