What this category's data looks like
This page addresses the scenario of annual progress and acceptance of research projects. Materials include annual progress reports, mid-term review materials, acceptance reports, as well as daily progress records, statistical scope notes, and external system receipts. The annual progress report, mid-term review materials, and acceptance report serve as mutual verification references for names, quantities, dates, and signatures; progress records and statistical scope notes enter the workflow as content to be verified, with the HTTP node sending requests to the external system. The update cadence is summarized weekly or monthly, and field characteristics center on project name, task number, start and end dates, completed quantity, signature status, and receipt number. The three types of materials respectively assume the following roles in the function: the annual progress report provides stage goals and milestones, the mid-term review materials provide mid-term indicators and exception notes, and the acceptance report provides the final conclusion and signature field; the fields of all three must correspond one by one in the request preview and returned fields.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The "progress table and statistical scope notes" are parsed from the response by subsequent nodes, or the external system handles them as agreed and then completes the process. The HTTP node does not replace the external system in writing to the database or approving; it only completes request sending and result return.
| Object | Check | Verification action |
|---|---|---|
| Annual progress report | Fields, dates, and signatures must be consistent with the progress records; names and quantities must not be misaligned between the two materials | Check the request body fields against the report header, use variables to trace the source of each placeholder, and compare the dates and signature status in the returned fields |
| Mid-term review materials | Mid-term indicators and exception notes must be stated in the statistical scope notes, and the quantity totals must match the number of records | In the request preview, view the fully rendered address, check the source of the Authorization request header value, and compare the returned fields with the quantities in the mid-term materials |
| Acceptance report | The final conclusion, signature, and receipt number must be consistent with what the external system returns; unsynchronized versions must be flagged | Use one sample request to compare the return, check the receipt field in responseData against the signature field of the acceptance report, and confirm the version number is consistent |
| Progress records and statistical scope notes | The number of records must match the statistical count, the scope must be written in the header, and exceptions must be noted one by one | Use one week of records to check the totals, inspect the header scope and exception notes, and check the request body fields against the external interface agreement |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the annual progress report and the mid-term review materials. Cause: The two materials are maintained separately and are not updated in sync from the same progress record as the source.
- Symptom: The acceptance report lacks a signature or receipt, and the external system's returned fields have no corresponding record. Cause: Signatures and receipts are not included in the request body fields, so subsequent nodes cannot parse the response to complete archiving.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The request header authentication information and request body fields are not passed in according to the external interface agreement, and variable placeholders are not resolved into actual values.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample; confirm that the three placeholders Authorization, variables, and responseData are all traceable.
Business test: use one week of records to check the totals, see whether the scope and exceptions are clearly written, whether the number of records matches the statistical count, and whether the header fields are consistent with the material names.
- In the variable panel, check the source of each placeholder and confirm that the variables in the request address, request headers, and request body can all be resolved into actual values.
- Use one sample request to compare the return, check that the request body fields are consistent with the external interface agreement, and record the number of array entries and the tokens of the referenced text.