What this category's data looks like
In the research funding budget adjustment and reimbursement scenario, materials fall into three categories: budget adjustment applications, reimbursement forms, and contract invoices. A budget adjustment application is usually submitted by the project leader and includes the adjusted subject, the amounts before and after adjustment, the reason for adjustment, and approval signatures; a reimbursement form includes expense details, dates, the handler's signature, and attachment receipts; a contract invoice includes the contract number, invoicing information, amount, and date. When the three types of materials enter the workflow, their roles differ: the budget adjustment application provides the basis for adjustment and the approval chain, the reimbursement form provides actual expenditures and vouchers, and the contract invoice provides external constraints and amount verification. The materials come from project team archives and financial system exports, and the update rhythm changes as budget adjustment approvals and reimbursement processes advance. In terms of field characteristics, names, quantities, dates, signatures, and version numbers are key anchors for cross-material comparison. The same record may have inconsistent names, quantities, or dates across different materials, and versions may not be synchronized or signatures and receipts may be missing, resulting in the inability to trace back to the original text during basis queries.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The basis entries that can be traced back to the original text 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 |
|---|---|---|
| Budget adjustment application | Whether the fields, dates, and signatures match the original text; whether the adjusted subject, the amounts before and after adjustment, and the approval signatures are complete and the version is current | Check the adjusted subject and amount in the application form, compare the approval signatures and dates, and confirm that the version number is consistent with the current version |
| Reimbursement form | Whether the expense details, dates, and handler's signature are consistent with the contract invoice; whether the names, quantities, and dates match | Compare the names, quantities, and dates in the reimbursement form and the contract invoice one by one, and check whether signatures and receipts are missing |
| Contract invoice | Whether the contract number, invoicing information, amount, and date can be traced back to the original text; whether the version is synchronized | Check the contract number and invoicing information, check the amount and date, and confirm that the version is synchronized and that no signatures or receipts are missing |
| User selection node | Each option corresponds to one branch; the interaction state is recorded; the selection result variable has been passed to subsequent nodes | Check the options and branch connections one by one in the node, trigger it once to view the node state in the run record, reference variables in subsequent nodes and run a trial; use nodeId to locate the node, and record the branch direction and interaction state |
Three common errors
- Symptom: The names, quantities, and dates of the same record do not match between the budget adjustment application and the reimbursement form. Cause: The two materials were entered separately, and no cross-material field comparison or version synchronization was performed.
- Symptom: The contract invoice version is not synchronized and still references the old amount and date. Cause: After the material was updated, the version number was not re-verified, and the workflow branch still continued execution according to the old version.
- Symptom: The reimbursement form lacks a signature or receipt, and the basis entry cannot be traced back to the original text. Cause: When the material was archived, the completeness of signatures and receipts was not checked, and the process stopped after the interaction was completed.
How to verify the setup
This feature's acceptance: run a trial for each option one by one, and check the branch direction and interaction state in the run record; reference variables in subsequent nodes to confirm that the selection result variable has been passed, use nodeId to locate the node, and record the branch direction.
Business test: ask a cross-material basis question and see whether the answer gives a traceable source; check that the basis comes from the institution’s materials, that the version is current, and that the entries match the original text.
- Run a trial of the user selection node for each option one by one, check the branch direction and interaction state in the run record, and confirm that the selection result variable has been passed to subsequent nodes.
- Perform cross-material field comparison on the budget adjustment application, reimbursement form, and contract invoice, and check whether names, quantities, dates, signatures, and versions are consistent and can be traced back to the original text.