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, and acceptance reports. Sources are submission forms submitted periodically by the project team and acceptance receipts returned by external systems, with an update cadence that rolls with review milestones. The three types of materials emphasize different fields: annual progress reports record task completion and fund execution, mid-term review materials record stage indicators and adjustment notes, and acceptance reports record overall conclusions and signature blocks. When materials enter this feature, annual progress reports and mid-term review materials usually serve as sources for request body fields, while acceptance reports mostly serve as the authorization basis for the external entry point, determining visitor identity and visible scope. The name, quantity, and date of the same record in the two types of materials must remain consistent, and versions and signature receipts must be synchronized; otherwise the externally visible scope will not match the settings.
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 external entry point and authorization scope are parsed from the response by subsequent nodes, or handled by the external system according to the agreement to complete the next step. The HTTP module sends requests to the target address. Path parameters, request body, and request headers can all use variable placeholders, and variables come from global variables, system variables, or outputs of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Annual progress report | Name, quantity, and date correspond item by item with the mid-term review materials, and signatures and receipts are complete | Check that the request body fields match the original report, compare the name and date of the same record in the two materials, and inspect the signature block |
| Mid-term review materials | The version is synchronized with the annual progress report, and field values can be traced to specific sources | In the variables panel, check the source of each placeholder and confirm that the fields in variables point to the latest version |
| Acceptance report | The authorization scope matches the visitor identity, and unauthorized access is not visible | Preview the rendered request and check the visible scope in the request header Authorization and the returned field responseData |
| Request address and path parameters | Placeholder variables can be resolved into actual values | View the full rendered address in the request preview |
Three common errors
- Symptom: The name, quantity, and date of the same record in the annual progress report and the mid-term review materials do not match. Cause: The two materials are filled in separately, without field-level comparison and version synchronization.
- Symptom: The visible scope of the external entry point exceeds the setting, and restricted identities see content that should not be visible. Cause: The authorization basis comes from an old version of the acceptance report, the version is not synchronized, and signatures and receipts are missing.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: Authentication information is not passed in as required by the external system, or placeholder variables cannot be traced to specific sources, causing value retrieval to fail.
How to verify the setup
Feature acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample; at the same time, check whether the values of Authorization, variables, and responseData are consistent with the agreement.
Business test: access once with a restricted identity and see whether the visible scope matches the setting
- Check the request header names and value sources, and confirm that authentication information is passed in as required by the external system
- Compare the response using one sample request, and confirm that the request body fields are consistent with the external interface agreement