What this category's data looks like
In the research funding budget adjustment and reimbursement scenario, three types of materials—budget adjustment applications, reimbursement forms, and contract invoices—enter the authorized access and external services stage at the same time. Budget adjustment applications record the account, amount, adjustment reason, and approval signature; reimbursement forms record expense details, the handler, and the reimbursement date; contract invoices record the contract number, invoiced amount, invoicing date, and signed receipt. The material sources are the research management system and the financial system, and the update cadence follows the approval flow and reimbursement progress. When entering this function, the budget adjustment application serves as the primary basis for the authorization scope, while reimbursement forms and contract invoices serve as auxiliary materials for the visible scope and field verification. The fields, dates, and signatures of the three types of materials must remain consistent; when the name, quantity, or date of the same record does not match across two materials, the authorization scope and externally visible content will deviate.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The externally available entry point and authorization scope are completed by subsequent nodes parsing the response, or by an external system handling it as agreed. The HTTP module sends requests to the target address, and variables can be used as placeholders in all three places: path parameters, request body, and request headers. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Budget adjustment application | Whether the authorization scope and visible fields are consistent with the account, amount, adjustment reason, and signature in the application | In the request preview, view the fully rendered address, verify the source of the Authorization request header value, and compare the account and amount in the returned fields |
| Reimbursement form | Whether the reimbursement details, handler, and reimbursement date match the authorization scope, and whether the fields are consistent with the external interface agreement | Use a sample request to compare the response, and verify whether the reimbursement form fields in responseData match the name, quantity, and date of the original document |
| Contract invoice | Whether the contract number, invoiced amount, invoicing date, and signed receipt are complete, and whether the version is synchronized | In the variables panel, verify the source of each placeholder, check whether the contract invoice fields in variables are missing a signature or receipt, and confirm that the version is not synchronized |
| Request address and path parameters | Whether the placeholder variables can be resolved into actual values, and whether the authentication information is passed in according to the external system's requirements | In the request preview, view the fully rendered address, verify the request header names and value sources, and confirm that the path parameters are resolved correctly |
Three common errors
- Symptom: The amount and date of the same budget adjustment do not match between the application and the reimbursement form. Cause: The two materials are entered separately, the versions are not synchronized, and the authorization scope is calculated based on the old version.
- Symptom: The contract invoice lacks a signature or receipt, but the external service still returns that record. Cause: When the materials enter the function, the signature and receipt fields are not validated, and the visible scope is not narrowed according to complete materials.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The authentication information is not passed in according to the external system's requirements, the request body fields are inconsistent with the external interface agreement, and the placeholder variables are not resolved into actual values.
How to verify the setup
Acceptance of this function: preview the rendered request, verify the status code and returned fields, and then compare the result against a sample.
Business test: access once with a restricted identity and see whether the visible scope matches the setting.
- In the variables panel, verify the source of each placeholder and confirm that
variablescan be traced to global variables, system variables, or the output of preceding nodes. - Use a sample request to compare the response, and verify whether the fields in
responseDataare consistent with the original records of the budget adjustment application, reimbursement form, and contract invoice.