What this category's data looks like
This page focuses on the research funding budget adjustment and reimbursement category. Materials include three types: budget adjustment applications, reimbursement forms, and contract invoices. Budget adjustment applications are initiated by the research group and record the account, amount, adjustment reason, and approval signature; reimbursement forms are filled out by the handler and include the matter, amount, date, and receipt number; contract invoices are issued by suppliers or partners and state the name, quantity, amount, and invoice date. The three types of materials play different roles when entering the workflow: budget adjustment applications serve as the prerequisite basis, reimbursement forms serve as execution evidence, and contract invoices serve as supporting attachments. The material sources are internal approval systems and external scanned receipts, and the update cadence advances in sync with approval nodes. Field characteristics center on name, quantity, date, signature, and receipt; the same record must remain consistent across different materials, and the version is based on the latest approval status.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Externally available entry points and authorization scope" is then completed by subsequent nodes continuing execution according to the branch. When the user selection 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 |
|---|---|---|
| Budget adjustment application | Whether the account name, adjustment amount, date, and signature in the application form and reimbursement form are consistent | Compare the fields of the two materials item by item, check whether the signature and receipt are complete, and check whether the fields referenced in variables are synchronized |
| Reimbursement form | Whether the name, quantity, amount, and invoice date in the reimbursement form and contract invoice match | Check the receipt number and amount, confirm that when the version is not synchronized the latest approval record prevails, and check whether the branch corresponding to nodeId is correct |
| Contract invoice | Whether the invoice name, quantity, and date match the budget adjustment application and reimbursement form | Compare the same record across the three materials, mark it as pending supplementation when a signature or receipt is missing, and confirm that the selection result variable passed by variables has taken effect |
| External entry point and authorization scope | Whether the visitor identity matches the visible scope, and whether unauthorized access is invisible | Access once with a restricted identity, check whether the scope of materials visible to that identity matches the setting, and record the interaction status and branch direction |
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: The two materials are entered separately, without field-level comparison and synchronization.
- Symptom: The contract invoice version is not synchronized, and the old invoice is still referenced. Cause: After approval advances, the attachment is not updated, and the workflow branch still points to the old record.
- Symptom: The reimbursement form lacks a signature or receipt, but the process still continues. Cause: The user selection node does not validate material completeness, and the branch directly enters the next stage.
How to verify the setup
This feature acceptance: Try running each option one by one, check the branch direction and interaction status in the run record, and confirm that the branch connections corresponding to variables and nodeId are correct.
Business test: Access once with a restricted identity, see whether the visible scope matches the setting, whether unauthorized materials are invisible, and whether the process continues downward after the interaction is completed.
- In the user selection node, check the options and branch connections one by one, trigger it once, and view the node status and selection result variable in the run record.
- Reference
variablesin a subsequent node and run it once to confirm that the selection result has been passed, and that after the interaction is completed the process has not stopped and has not re-entered the interaction.