Workflow Orchestration for Research Outcome Registration and Intellectual Property: Maintain Document Versions and Changes

Research IP: review workflows for version tracking. Compare the source records, required inputs and downstream results before handing the task over.

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 come from research group submissions, with fields including achievement name, completers, date, and signature; patent disclosure documents come from inventor writing, with fields including technical solution, inventor, filing date, and receipt; software copyright materials come from development team compilation, with fields including software name, version number, copyright holder, and seal. The three types of materials have different update rhythms: registration forms are supplemented as achievements are produced, disclosure documents are revised as patent progress advances, and copyright materials are replaced as versions iterate. After materials enter the workflow, the registration form assumes the role of the master record, the disclosure document assumes the role of the technical source, and the copyright materials assume the role of version comparison; the fields and dates of the three must remain traceable in the branch flow.

Configuration and implementation checks

This stage is executed by workflow nodes (user selection and branching), outputting branch flow and interaction state records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.

ObjectCheckVerification action
Achievement registration formWhether the name, completers, date, and signature are consistent with the disclosure documentCheck the options and branch connections one by one in the node, reference variables, and run a trial once
Patent disclosure documentWhether the technical solution, inventor, filing date, and receipt match the registration formTrigger a user selection once and check the node status in the run records
Software copyright materialsWhether the software name, version number, copyright holder, and seal are in sync with the current versionReference the variable corresponding to nodeId in a subsequent node and run a trial once
Version ledger and change recordsThe current version is unique, old versions are traceable, and references are in syncChange one piece of content and see whether the version number and references are updated in sync

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 submitted separately, and field comparison is not performed in the branch flow.
  • Symptom: The version of the software copyright materials is not synchronized, and the old version is still referenced. Cause: The process stops after the interaction is completed, and subsequent nodes do not continue execution according to the branch to update.
  • Symptom: The disclosure document lacks a signature or receipt, and the signature field of the registration form is blank. Cause: The user selection node does not record the interaction state, and the branch flow cannot be traced.

How to verify the setup

This feature's acceptance: run trials option by option, check the branch flow and interaction state in the run records, and verify the transfer results of variables and nodeId.

Business test: change one piece of content and see whether the version number and references are updated in sync.

  • Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
  • Trigger a user selection once, check the node status in the run records, and confirm that after the interaction is completed, execution continues along the branch corresponding to the selected option.