What this category's data looks like
Annual progress reports are updated by annual cycle, mid-term inspection materials are submitted by milestone, and acceptance reports are consolidated at the project closing stage. When the three types of materials enter this function, the annual progress report takes the role of stage results and date records, the mid-term inspection materials take the role of process verification and receipts, and the acceptance report takes the role of final conclusions and signatures. Field characteristics are concentrated in name, quantity, date, and signature fields; version numbers and receipt numbers are key to tracing. The update rhythm determines that the same record may appear in multiple materials, requiring cross-comparison by version and date.
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 "exception list and review conclusions" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the follow-up. The request URL, path parameters, request headers, and request body can all be placeheld via variables, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Annual progress report | Name, quantity, date, and signature fields must be consistent with the mid-term inspection materials | Check the fully rendered URL in the request preview, and compare the fields returned by responseData with the report fields |
| Mid-term inspection materials | When the name, quantity, and date of the same record do not match across the two materials, mark it as an exception | Verify the name and value source of the request header Authorization, and spot-check the receipt number |
| Acceptance report | If the version is not synchronized or signatures or receipts are missing, it enters manual review | Use one sample request to compare the return, and verify the source of each variables placeholder |
| Exception list and review conclusions | Exceptions are supported by original records and, after the reviewer signs, are handed to the person in charge for handling | Check whether the conclusion fields generated after subsequent nodes parse the response are complete |
Three common errors
- Symptom: the name and quantity of the same record do not match between the annual progress report and the mid-term inspection materials. Cause: the versions of the two materials are not synchronized, and the field value sources differ.
- Symptom: the acceptance report lacks a signature or receipt, and the exception list cannot be closed. Cause: the signature field and receipt number were not updated with the version, and the manual review step was omitted.
- Symptom: the request returns 401 or the external system receives empty fields. Cause: the
Authorizationvalue source is wrong, or thevariablesplaceholders were 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; check whether the responseData fields are consistent with the external interface agreement.
Business test: create one exception record, see whether it can be traced back to the source material, and check the name, quantity, date, and signature fields of the annual progress report, mid-term inspection materials, and acceptance report.
- In the variable panel, verify the source of each
variablesplaceholder, and confirm that it can be traced to a global variable, system variable, or the output of a preceding node. - Verify the name and value source of the request header
Authorization, and use one sample request to compare the fields returned byresponseData.