What this category's data looks like
At the stage of signing research project task books, the category materials include the project task book, the topic task breakdown table, and the budget book. They are sourced from collaborative submission by the research management department and the project undertaking unit, and the update cadence refreshes in sync with project approval, task adjustments, and budget verification. The field characteristics of the three types of materials center on project name, topic number, undertaking unit, start and end dates, funding amount, signature, and receipt. When entering the authorized access and external service function, the project task book serves as the main record providing the external entry point and the baseline for authorization scope, the topic task breakdown table serves as the basis for splitting the visible scope at the topic level, and the budget book constrains the granularity of external disclosure of funding fields; together, the three determine the matching relationship between visitor identity and visible scope, and unauthorized content is not visible.
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 externally available entry point and authorization scope are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to continue completion. The request URL, request headers, and placeholder variables in the request body come from global variables, system variables, or outputs of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Project task book | The project name, start and end dates, and signature receipt must align item by item with the topic task breakdown table | Verify that the request body fields are consistent with the project task book fields, compare whether the dates and signatures are complete, and check the placeholder sources in the variables panel |
| Topic task breakdown table | The topic number, undertaking unit, and quantity must be consistent with the same record in the project task book | Use one sample request to compare the returned fields, and check whether the topic-level visible scope matches the authorization scope |
| Budget book | The funding amount and budget subjects must be consistent with the same record in the project task book | Check the request header names and value sources, and confirm that authentication information is passed in according to the external system's requirements |
| Request URL and path parameters | Placeholder variables can be resolved into actual values | View the fully rendered URL in the request preview, and check whether variables and responseData are traceable |
Three common errors
- Symptom: The name, quantity, and dates of the same record do not match between the project task book and the topic task breakdown table. Cause: The two materials are submitted separately, without field-level alignment and receipt confirmation.
- Symptom: The budget book version is not synchronized, and the funding amount is inconsistent with the task book. Cause: After budget verification, the task book was not written back, the version was not synchronized, and signatures or receipts are missing.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The source of the
Authorizationvalue was not checked, and placeholder variables were not resolved into actual values.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample; check whether 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.
- In the variables panel, check the source of each placeholder and confirm that the placeholders in the request URL, request headers, and request body can all be resolved into actual values.
- Check the request header names and value sources, and use one sample request to compare whether the returned fields are consistent with the external interface agreement.