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 forms record the name, contributors, date, and signature; patent disclosure documents contain the technical solution, inventors, filing date, and receipt; software copyright materials include the software name, version number, ownership, and seal. When these three types of materials enter authorized access and external services, the registration form serves as the primary record entry point, while disclosure documents and copyright materials serve as supporting attachments. Field characteristics center on name, quantity, date, signature, and version number. Material sources are internal submissions and external receipts, and the update cadence changes with approval and registration status, requiring version synchronization.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. "Externally available entry points and authorization scope" are parsed from the response by subsequent nodes, or handled by the external system according to the agreement to complete the next step. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | Name, quantity, date, and signature must match the supporting materials item by item | Verify the rendered address in the request preview, and check the fields returned by responseData |
| Patent disclosure document | Inventor, filing date, and receipt number must match the corresponding record in the registration form | Check the source of the Authorization value in the request header, and confirm that authentication information is passed in according to the external system's requirements |
| Software copyright materials | Software name, version number, and ownership must be synchronized with the registration form version | Check each placeholder source in the variables panel, and confirm that variables can be traced to a specific origin |
| Request body | Fields must be consistent with the external interface agreement; compare the return using a sample request | Use one sample request to compare the return, and confirm empty fields and timeout conditions |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match across two materials. Cause: The registration form and the disclosure document are maintained separately, without field-level comparison.
- Symptom: The version is not synchronized, and an old version number is returned externally. Cause: After the copyright materials are updated, they are not written back to the registration form, and the request body still uses the old variables.
- Symptom: A signature or receipt is missing, and the response body fields are empty. Cause: The materials enter the request process before signing is completed, and the external system receives empty fields.
How to verify the setup
Preview the rendered request, check the status code and returned fields, then compare the result against one sample; confirm that the three identifiers Authorization, variables, and responseData can all be mapped to actual values.
Business test: access once with a restricted identity, and see whether the visible scope matches the setting.
- In the request preview, view the complete rendered address, and confirm that path parameter placeholder variables are resolved into actual values.
- In the variables panel, check each placeholder source, and confirm that the request header names and value sources meet the external system's requirements.