What this category's data looks like
This page focuses on material drafting and responsibility handover in the context of research funding budget adjustments and reimbursements. Material sources include three categories: budget adjustment applications, reimbursement forms, and contract invoices, with an update cadence that rolls forward according to funding execution progress and financial review milestones. Budget adjustment applications record accounts, amounts, reasons, and approval chains; reimbursement forms carry expense details, receipt numbers, and handlers; contract invoices provide transaction evidence and invoicing information. When these three categories of materials enter workflow orchestration, they play the roles of initiation basis, execution evidence, and compliance working papers, respectively, jointly supporting the generation of issuable drafts and handover records. Field characteristics center on name, quantity, date, signature, and version number; if any field is inconsistent between two materials, an interception is triggered.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. Issuable material drafts and handover records are completed by subsequent nodes continuing execution along the branches. 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 | Accounts, amounts, reasons, dates, and signatures are complete, and the version number is consistent with the reimbursement form | Check the options and branch connections one by one in the node, and verify whether the application fields are covered by the branch conditions |
| Reimbursement form | Expense details, receipt numbers, and handler signatures match the name, quantity, and date on the contract invoice | Trigger a user selection once, and check the node status and selection result variables in the run record |
| Contract invoice | Invoicing information, contract number, and amount are consistent with the reimbursement form records, and the receipt is complete | Reference variables in subsequent nodes and run a trial once to confirm the branch direction and interaction state records |
| Handover record | The responsible person is clear, the receipt time is consistent with the version date, and missing items are intercepted | Draft one according to the template and complete one handover, then verify whether the branch corresponding to nodeId executes according to the option |
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 drafted separately, without field-level comparison and version synchronization.
- Symptom: The contract invoice version is not synchronized, and the reimbursement form still references the old amount. Cause: The update cadence is not synchronized, and there is a lack of verification of consistency between version number and date.
- Symptom: The handover record lacks a signature or receipt, but the process still continues. Cause: The branch conditions do not cover the signature and receipt fields, so missing items are not intercepted.
How to verify the setup
Feature acceptance: Run trials option by option, check the branch direction and interaction state in the run record, and confirm that variables have been passed to subsequent nodes and that the branch corresponding to nodeId is correct.
Business test: Draft one according to the template and complete one handover, and see whether missing items are intercepted.
- Check the options and branch connections one by one in the node to ensure each option corresponds to one branch.
- Reference the selection result variable in subsequent nodes and run a trial once to check whether the process continues after the interaction is completed.