What this category's data looks like
This category's data covers three types of materials involved in National Key R&D Program project applications: the project application form, the budget application form, and the cooperation agreement. Fields, dates, and signatures must be consistent item by item. The project application form carries the project name, principal investigator, start and end dates, and indicators; the budget application form carries subject amounts, calculation basis, and matching funds; the cooperation agreement carries partner units, task division, signatures and seals, and receipts. When the materials enter the HTTP interface and external systems, the application form provides the subject and authorization scope, the budget form provides the amounts and subjects, and the agreement provides the signatures and seals and the basis for external services. The update cadence follows application milestones and version iterations, and the field characteristics are multi-table same-source, date-sensitive, and signature-and-seal traceable.
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 handled by subsequent nodes parsing the response, or by the external system continuing according to the agreed convention. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Project application form | Name, quantity, and dates must be aligned item by item with the budget application form and the cooperation agreement, and signatures and receipts must be complete | In the request preview, view the rendered full address, and check the request body fields against the sample response |
| Budget application form | Subject amounts, calculation basis, and matching funds must be consistent with the project application form and the cooperation agreement | Check the request header names and the source of their values, and confirm that authentication information is passed in as required by the external system |
| Cooperation agreement | Partner units, task division, signatures and seals, and receipts must be synchronized with the versions of the two application forms | In the variables panel, check the source of each placeholder and confirm that variables can be traced to a specific origin |
| Request address and path parameters | Placeholder variables can be resolved into actual values, and the returned fields are consistent with the agreement | Use one sample request to compare responseData, and check whether Authorization is passed in as agreed |
Three common errors
- Symptom: The name, quantity, and dates of the same record do not match between the project application form and the budget application form. Cause: The two materials are maintained separately, without cross-checking and version synchronization.
- Symptom: The cooperation agreement lacks a signature or receipt, yet the external service entry point is still allowed through. Cause: The authorization scope determination does not include signatures and seals and receipts as visibility conditions.
- 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 the source of placeholder variables is unclear.
How to verify the setup
Acceptance of this feature: preview the rendered request, check the status code and returned fields, then compare the result against one sample to confirm that responseData is consistent with the agreement.
Business test: access once with a restricted identity, and see whether the visible scope matches the setting, with unauthorized access not visible.
- In the variables panel, check the source of each placeholder and confirm that
variablescan be traced to global variables, system variables, or the output of preceding nodes - Check the request header names and the source of their values, and confirm that
Authorizationis passed in as required by the external system