What this category's data looks like
Research achievement registration and intellectual property management involves three types of materials: achievement registration forms, patent disclosure documents, and software copyright materials. Achievement registration form fields include achievement name, contributors, date, and signature; patent disclosure documents include technology name, inventor, filing date, and receipt; software copyright materials include software name, version number, copyright owner, and seal. The materials come from R&D, legal, and research management departments and are aggregated and updated weekly or monthly. When entering this function, the achievement registration form serves as the record primary key and statistical base, the patent disclosure document provides application progress and external receipts, and the software copyright materials supplement ownership and version information. The three types of materials need to be cross-aligned on name, quantity, date, and signature. The HTTP node is responsible for sending the aggregation request to the external system, and the returned fields are used by subsequent nodes for verification.
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 progress table and statistical scope description are completed by subsequent nodes parsing the response, or by the external system handling it as agreed.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | Whether the fields, date, and signature are complete, and whether the record count matches the statistical count | Check the achievement name, contributors, date, and signature fields, and compare with the weekly report totals |
| Patent disclosure document | Whether the technology name, filing date, and receipt are consistent with the registration form | Use one sample request to compare the returned fields, and check the date and receipt number |
| Software copyright materials | Whether the software name, version number, and seal are updated synchronously | Check the version number and seal, and confirm they are consistent with the name in the registration form |
| HTTP request | Whether the request URL, request headers, and placeholder variables in the request body can be resolved into actual values | View the fully rendered URL in the request preview, and check the sources of Authorization, variables, and responseData |
Three common errors
- Symptom: The name, quantity, or date of the same achievement does not match between the registration form and the disclosure document. Cause: The two materials are filled in by different nodes separately and are not aligned by the same record primary key.
- Symptom: The version number in the software copyright materials is inconsistent with the registration form, and the receipt is missing. Cause: The version was not synchronized, and the signature or receipt was not updated with the materials.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The request header authentication information was not passed in as required by the external system, or the placeholder variables were not resolved into actual values.
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 one sample to confirm that responseData is consistent with the agreed fields.
Business test: use one week of records to check the totals, see whether the scope and exceptions are clearly stated, and confirm that the record count matches the statistical count.
- In the variable panel, check the source of each placeholder and confirm that
Authorization,variables, andresponseDatacan all be traced to global variables, system variables, or outputs from preceding nodes. - Check the request header names and value sources, use one sample request to compare the response, and check whether the external system receives empty fields.