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. The sources are submissions from research groups and archiving by management departments, and the update cadence rolls forward with application cycles and review milestones. Achievement registration forms record the achievement name, contributors, date, and signature; patent disclosure documents carry the technical solution, inventors, filing date, and receipt; software copyright materials include the version number, development completion date, seal, and acceptance receipt. When the materials enter the authorized access and external services workflow, each plays a different role: achievement registration forms are used to determine achievement ownership and publicly disclosable fields, patent disclosure documents are used to define the visibility boundary of the technical content, and software copyright materials are used to verify the version and rights status. The fields of the three must stay consistent in name, quantity, date, signature, and receipt; after version synchronization they enter branch selection, so that parents or superiors can view the corresponding scope by identity.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting the branch direction and interaction state records. "Externally available entry points and authorization scope" is then completed by subsequent nodes continuing execution along the branch. On trigger, the conversation enters the interaction state and the workflow state is recorded; after the user completes the selection, execution continues along the branch corresponding to the chosen option.
| Object | Check | Verification action |
|---|---|---|
| Achievement registration form | Whether the name, contributors, date, and signature are consistent with the patent disclosure document | Check the options and branch connections one by one in the node, and reference variables to see whether the selection result variable is passed to subsequent nodes |
| Patent disclosure document | Whether the technical solution, inventors, filing date, and receipt match the software copyright materials | Trigger one interaction, view the node status in the run record, and check the branch direction corresponding to nodeId |
| Software copyright materials | Whether the version number, development completion date, seal, and acceptance receipt are synchronized | Reference this variable in a subsequent node and do a trial run to confirm that the version and date do not show inconsistency between the two materials |
| User selection node | Each option corresponds to one branch, and unauthorized identities cannot see the corresponding scope | Trial-run each option one by one, check the branch direction and interaction state in the run record, and confirm that restricted identities do not enter the external branch |
Three common errors
- Symptom: the name, quantity, and date of the same achievement do not match across the two materials. Cause: the achievement registration form and the patent disclosure document are maintained separately, and field comparison was not done before entering the branch.
- Symptom: the version is not synchronized, and the version numbers of the software copyright materials and the patent disclosure document are inconsistent. Cause: after the materials were updated, re-selection was not triggered, and subsequent nodes still continued execution along the old branch.
- Symptom: a signature or receipt is missing, yet the external entry point can still be accessed by a restricted identity. Cause: the authorization scope was not updated with the signature and receipt status, and the basis for branch judgment did not cover material completeness.
How to verify the setup
This feature's acceptance: trial-run each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, and that the selection result variable has been passed to subsequent nodes.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, confirm that unauthorized content is not visible, and that the scope opened to parents or superiors is consistent with the branch direction.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and check the values of
variablesandnodeIdin the run record. - After triggering one interaction, view the node status in the run record, confirm that the process continues downward after the interaction completes, and that the same session does not re-enter the interaction.