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. The achievement registration form records the achievement name, contributors, date, and signature, and is used for intake registration and assignment of handling; the patent disclosure document carries the technical solution, inventors, application milestones, and signature receipt, and is used to determine the type of intellectual property and the items to be completed; the software copyright materials include source code, specification, version number, and seal, and are used to verify the version and ownership. In the Q&A intake step, the three types of materials together form the basis for missing-item identification: the registration form determines the subject and date, the disclosure document determines the technical content and signature, and the copyright materials determine the version and receipt. Materials enter in the form of forms and attachments, and the update rhythm changes with achievement progress and version iterations. Field characteristics are concentrated in five categories: name, quantity, date, signature, and receipt. Any inconsistency in any one of them will trigger a follow-up question.
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 intake record and the completion questions are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the process. The request URL, path parameters, request headers, and request body can all reference variables via {{}}. The variables come from global variables, system variables, or the output of preceding nodes; Authorization is passed in according to the external system's requirements, and the returned responseData is parsed by subsequent nodes.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | The name, quantity, date, and signature must align with the disclosure document and copyright materials; if any field does not match, it is listed as a missing item | Retrieve the registration form and disclosure document, compare the name, quantity, and date field by field, and check whether the signature column and receipt are complete |
| Patent disclosure document | The technical solution, inventors, application date, and signature receipt must be consistent with the registration form, and the version number must not lag behind | Use a sample request to compare the returned fields, check the name and date in responseData, and inspect the signature and receipt |
| Software copyright materials | The source code, specification, version number, and seal must be synchronized with the registration form and disclosure document; if the version is not synchronized, follow up | Check the version number and seal, confirm the source of each placeholder in the variables panel, and inspect the values of variables and Authorization |
| HTTP request response | The status code and returned fields must be consistent with the external interface agreement; empty fields and timeouts must be recorded separately | View the fully rendered URL in the request preview, check the request header names and value sources, and compare the results with a sample request |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match across two materials. Cause: The registration form and disclosure document were entered separately, and no field-level comparison was performed.
- Symptom: The version is not synchronized, and the version numbers in the copyright materials and the disclosure document are inconsistent. Cause: The materials were submitted in batches, and the update rhythm was not aligned.
- Symptom: A signature or receipt is missing, but the intake record is still advanced. Cause: Missing-item identification did not cover the signature column and receipt fields.
How to verify the setup
Acceptance of this feature: preview the rendered request, check the status code and returned fields, then compare the result against a sample; inspect the responseData fields and the sources of variables.
Business test: submit a question missing key information and see whether it asks a follow-up question before answering.
- In the request preview, check the fully rendered URL and request header names, and confirm the source of the
Authorizationvalue. - In the variables panel, check the origin of each placeholder, and use a sample request to compare the returned fields and status code.