What this category's data looks like
This category's data covers three types of materials: achievement registration forms, patent disclosure documents, and software copyright materials. Achievement registration forms record the achievement name, contributors, date, and signature/seal; patent disclosure documents carry the technical solution, inventors, application milestones, and signed confirmation; software copyright materials include source code, specifications, copyright owner information, and receipts. When these materials enter the data versioning and change maintenance function, each plays a different role: the achievement registration form serves as the primary record source for the version ledger, while patent disclosure documents and software copyright materials serve as associated attachments and citation references. Material sources include archiving by the research management department, return transmissions from agencies, and submissions by inventors. The update cadence varies with registration status, review milestones, and correction requirements, and the field characteristics center on names, quantities, dates, signatures, and receipts.
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 "version ledger and change records" are completed by subsequent nodes parsing the response, or by an external system handling it as agreed. The request URL, path parameters, request headers, and request body can all use variable placeholders, with variables coming from global variables, system variables, or outputs of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | The name, quantity, date, and signature remain unique to the current version in the version ledger | Check whether the registration form fields align with the ledger records, and verify whether the signature and receipt are complete |
| Patent disclosure document | The inventors, technical solution, and application date are consistent across both materials | Compare the name, quantity, and date in the disclosure document and the registration form, and confirm that citations are in sync |
| Software copyright materials | The copyright owner, version number, and receipt information can be traced to the current version | Check the material version number against the citation source, and confirm that the old version is traceable and the new version is unique |
| Request response | The status code and returned fields can locate the specific record | View the fully rendered URL in the request preview, and compare the returned fields using a sample request |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the achievement registration form and the patent disclosure document. Cause: The two materials are maintained separately, without field comparison against the current version as the standard.
- Symptom: The version is not synced, and the old version is still referenced. Cause: After a change, the citation source was not updated, and the knowledge base or external documents still point to the old record.
- Symptom: A signature or receipt is missing, and the material cannot proceed to the next node. Cause: The registration form or copyright materials have not completed signature/seal and receipt archiving, and are blocked when the external system handles them as agreed.
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; also check whether the three placeholders Authorization, variables, and responseData are parsed into actual values.
Business test: change one piece of content and see whether the version number and citations are updated in sync.
- In the variables panel, check the source of each placeholder, and confirm that the request header names and value sources meet the external system's requirements
- Use a sample request to compare the returned fields against the external interface agreement, and confirm that the request body fields are consistent