What this category's data looks like
The data in this category looks like this: Research achievement registration and intellectual property management involve three types of materials: achievement registration forms, patent disclosure documents, and software copyright materials. Achievement registration forms are filled out by the research group and include the achievement name, completers, date, and signature of the person in charge; patent disclosure documents are submitted by the inventors and include the technical solution, order of inventors, and filing date; software copyright materials include a source code list, version number, and seal of the copyright owner. When these three types of materials enter the abnormal traceability and manual review function, the registration form serves as the main record, while the disclosure document and copyright materials serve as supporting evidence, used to compare the name, quantity, date, and signatures of the same achievement. The update rhythm of materials changes with application milestones, and failure to synchronize old versions after version iteration is a common source. The field characteristics are multi-source, multi-version, and scattered signatures and receipts, requiring item-by-item tracing back to the source materials.
Configuration and implementation checks
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 exception list and review conclusions are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the next step. The HTTP module sends requests to the target address. Variables can be used as placeholders in three places: path parameters, request body, and request headers. Variables come from global variables, system variables, or outputs from preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | Whether the name, quantity, date, and signature are consistent with the disclosure document | Compare the achievement registration form and the patent disclosure document field by field, verify the date and the signature of the person in charge, and use variables in the request body to reference the registration form fields |
| Patent disclosure document | Whether the order of inventors, filing date, and receipt are complete | Verify the order of inventors and filing date in the disclosure document, check whether the acceptance receipt is missing a signature, and pass Authorization in the request header according to the external system's requirements |
| Software copyright materials | Whether the version number, copyright owner, and seal are synchronized | Compare whether the version number in the copyright materials matches the version in the registration form, verify the copyright owner's seal, and check the fully rendered address in the request preview |
| Exception list and review conclusions | Whether the exception is traced back to the source material and has the reviewer's signature | Use a sample request to compare the response, and check whether the responseData field contains the exception number, source material identifier, and reviewer's signature |
Three common errors
- Symptom: The name, quantity, and date of the same achievement do not match between the registration form and the disclosure document. Cause: The two materials were filled out by different personnel at different times without cross-checking.
- Symptom: The version of the software copyright materials is not synchronized, and the old version's seal is still referenced. Cause: After version iteration, the registration form was not updated, and material circulation lacks version locking.
- Symptom: The disclosure document is missing the inventor's signature or the acceptance receipt is missing. Cause: The submission step did not validate the signature and receipt fields, and the external system received empty fields.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, and then compare the result against one sample.
Business test: create an exception record and see whether it can be traced back to the source material.
- In the variables panel, check the source of each placeholder and confirm that the request address and path parameters can be resolved into actual values.
- Check the request header names and value sources, use a sample request to compare the response, and confirm that the request body fields are consistent with the external interface agreement.