What this category's data looks like
During the signing stage of a research project task book, the materials include the project task book, the subject task breakdown table, and the budget book; the fields, dates, and signatures of the three must correspond to one another. The project task book defines the overall objectives and the signature of the person in charge, the subject task breakdown table splits the subjects and their undertakers, and the budget book lists budget subjects and amounts. The materials come from declaration system exports or offline stamped scans, are updated along with the signing process, and the final signed version prevails. When entering the exception tracing and manual review function, the project task book serves as the main record anchor, and the subject task breakdown table and budget book serve as the basis for comparison, used to discover situations such as mismatched names, quantities, or dates for the same record, unsynchronized versions, and missing signatures or receipts, forming an exception list and review conclusions.
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 and completed by an external system according to an agreement. The HTTP node only sends requests to the target address; it does not write to the database or approve on behalf of the external system.
| Object | Check | Verification action |
|---|---|---|
| Project task book | Check whether the project name, person in charge, signing date, and signature are consistent with the subject task breakdown table | In the request preview, view the full rendered address, use the variables placeholders to compare field sources, and check the Authorization request header |
| Subject task breakdown table | Check whether the subject name, undertaker, and start and end dates match the project task book | Compare the names, quantities, and dates of the two materials item by item, and check the source of each placeholder in the variables panel |
| Budget book | Check whether the budget subjects and amounts are consistent with the project task book and the subject task breakdown table | Use a sample request to compare the response, and check whether the responseData fields correspond to the budget entries |
| Exception record | Check whether the exception is supported by the original record and whether the reviewer has signed | Create an exception record, see whether it can be traced back to the source material, and check whether the returned fields contain the original record identifier |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the project task book and the subject task breakdown table. Cause: The two materials were entered separately, and no field-level comparison was performed.
- Symptom: The budget book version is not synchronized, and the amount is inconsistent with the task book. Cause: The signing process involved multiple revisions, and the final signed version was not taken as the standard.
- Symptom: Signatures or receipts are missing, and the exception cannot be traced. Cause: Offline signing was not returned, and the HTTP request returns empty fields or times out.
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 a sample, confirming that the sources of responseData and variables are traceable.
Business test: create an exception record, see whether it can be traced back to the source material, and check whether the exception list and review conclusions are supported by the original record and the reviewer's signature.
- In the request preview, check the full rendered address, request headers, and request body, and confirm that each placeholder variable can be traced to a global variable, system variable, or the output of a preceding node.
- Use a sample request to compare the response, check the status code and returned fields, and hand the exception list and review conclusions to the person in charge for handling.