What this category's data looks like
At the signing stage of a research project task book, three types of materials are involved: the project task book, the subject task breakdown table, and the budget book. The task book is provided by the project lead, and states the research content, assessment indicators, and signature page; the breakdown table is filled in by the subject leader, and splits tasks, milestones, and responsible persons; the budget book is prepared by the finance or research management department, and lists budget subjects, amounts, and matching sources. The three types of materials are updated synchronously at signing, and their field characteristics include project number, subject name, start and end dates, task volume, amount, signature, and receipt status. When entering progress records and statistical verification, the task book is the source of the overall scope, the breakdown table provides executable task items, and the budget book constrains resources and milestones. Materials are summarized weekly or monthly to form a progress table and statistical scope description, for subsequent verification of whether the number of records and the statistical number are consistent.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, and outputs the response body, status code, and returned fields. The progress table and statistical scope description are parsed from the response by subsequent nodes, or processed by an external system according to the agreement to complete the rest. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Project task book | Check the project number, subject name, start and end dates, and signature field, and determine whether they are consistent with the breakdown table and budget book | View the rendered full address in the request preview, check the source of the Authorization request header value, and confirm that the returned fields include the project number and signing status |
| Subject task breakdown table | Check the task item name, quantity, milestone date, and responsible person, and determine whether they match the task book and budget book | Use one sample request to compare the response, and check whether each placeholder in variables can be traced to a specific field in the task book or breakdown table |
| Budget book | Check the budget subjects, amounts, matching sources, and budget date, and determine whether the quantities and dates are consistent with the task book and breakdown table | Check whether the fields returned in responseData include budget subjects and amounts, and confirm consistency with the budget book header scope |
| Progress table and statistical scope description | Check whether the number of records equals the statistical number, whether the scope is written in the header, and whether exceptions are noted | Use one week of records to check the total, and verify item by item the correspondence of names, quantities, and dates among the three types of materials |
Three common errors
- Symptom: the name and quantity of the same subject do not match between the task book and the breakdown table. Cause: the two materials are filled in by different roles, and field-level verification was not done before signing.
- Symptom: the budget book version is not synchronized, and the amount is inconsistent with the task book date. Cause: after modification, only one material was updated, without receipt confirmation.
- Symptom: signature or receipt is missing, and it cannot be determined during statistics whether the record is valid. Cause: the signing process did not write the receipt status into the progress table.
How to verify the setup
This feature acceptance: view the rendered full address in the request preview, check the status code and returned fields, then compare the result against one sample, and confirm the values and sources of Authorization, variables, and responseData.
Business test: use one week of records to check the total, see whether the scope and exceptions are clearly written, and whether the number of records matches the statistical number.
- In the variables panel, check the source of each placeholder, and confirm that the variables in the request address, request headers, and request body can be parsed into actual values.
- Use one sample request to compare the returned fields, check whether the external system received empty fields, and verify whether the names, quantities, and dates in the response are consistent with the three types of materials.