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 are submitted by research groups after project completion and are aggregated and updated quarterly; fields include achievement name, completers, completion date, registration number, classification level, and signature field. Patent disclosure documents are written by inventors and updated along with application milestones; fields include technical solution, inventors, application date, priority information, and drawing list. Software copyright materials are compiled by the development team and updated according to the version release cadence; fields include software name, version number, development completion date, ownership, and signature/seal page. When these three types of materials enter workflow orchestration, the achievement registration form serves as the master record source, while patent disclosure documents and software copyright materials serve as derived materials. They must remain consistent with the master record in name, quantity, date, signature, and receipt. If any field is missing or a version is not synchronized, an interception is triggered.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The material drafts and handover records that can be issued are completed by subsequent nodes continuing execution according to the branch. When a node is triggered, the conversation enters an interactive state and the workflow state is recorded. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | Fields are complete: achievement name, completers, completion date, registration number, classification level, and signature field are checked item by item; date and version are consistent | In the node, check the options and branch connections one by one, reference variables and nodeId, and check the node status in the run record |
| Patent disclosure document | The name, quantity, and date match the same record as the achievement registration form; inventor signatures and receipts are complete | In subsequent nodes, reference the selection result variable and run a test once to check whether variables has been passed to subsequent nodes |
| Software copyright materials | The version number and development completion date are synchronized; ownership and signature/seal page are complete, with no missing signatures or receipts | Trigger a user selection once and check the nodeId status and branch direction in the run record |
| Handover record | The responsible person is clear, the version and date are consistent, and the receipt is complete | Draft one according to the template and complete one handover to see whether missing items are intercepted |
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 filled in independently, without field comparison using the master record as the baseline.
- Symptom: The version number and development completion date of the software copyright materials are not synchronized. Cause: After a version update, the registration form is not written back, and the derived materials continue to use the old version information.
- Symptom: The handover record lacks a signature or receipt, but the process still moves forward. Cause: The signature and receipt fields are not set as required, and the branch judgment does not intercept missing items.
How to verify the setup
Acceptance for this feature: run tests on each option one by one, check the branch direction and interaction state in the run record, and confirm that variables, nodeId, and option branches correspond one to one.
Business test: draft one according to the template and complete one handover to see whether missing items are intercepted.
- In the node, check the options and branch connections one by one, and confirm that each option corresponds to one branch.
- In subsequent nodes, reference the selection result variable and run a test once to confirm that the selection result has been passed to subsequent nodes.