What this category's data looks like
This category covers the investigation and handling of academic misconduct reports. Materials include report materials, investigation reports, expert appraisal opinions, and receipt and signature pages. Sources are paper or electronic documents formed at each stage of acceptance registration, investigation and evidence collection, expert review, and deliberation decisions, and the update cadence changes as the investigation stages advance and supplementary appraisals are added. Field characteristics center on the reported person's name, paper title, alleged facts, evidence number, investigation date, appraisal conclusion, and signature and receipt status. When materials enter workflow orchestration, report materials serve as the trigger input, investigation reports serve as the intermediate verification object, expert appraisal opinions serve as the basis for branch decisions, and receipt and signature pages serve as the closing condition. If the name, quantity, or date of the same record does not match across two materials, or if versions are not synchronized, or signatures or receipts are missing, subsequent nodes will continue executing along the wrong branch.
Configuration and implementation checks
This part is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "version ledger and change records" are completed by subsequent nodes continuing execution along the branch. When the user selection 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 chosen option.
| Object | Check | Verification action |
|---|---|---|
| Report materials | Whether the fields include the reported person, paper title, alleged facts, evidence number, acceptance date, and signature | Compare item by item against the acceptance registration form, verify the name, quantity, date, and signature column, and confirm consistency with the citations in the investigation report |
| Investigation report | Whether the fields include the investigation process, evidence list, conclusion, investigator, and date | Check the options and branch connections one by one in the node, and check whether the evidence numbers cited in the report correspond to the report materials |
| Expert appraisal opinion | Whether the fields include the appraisal matter, opinion conclusion, expert signature, and appraisal date | Compare the conclusion in the investigation report with the appraisal opinion, and check whether the date, signature, and receipt are complete |
| Version ledger and change records | Whether the current version is unique, old versions are traceable, and citations are synchronized | After changing one piece of content, run a test to check whether the version number and citations are updated synchronously, and record variables, nodeId, and the branch direction |
Three common errors
- Symptom: the name, quantity, or date of the same piece of evidence does not match across two materials. Cause: acceptance registration and the investigation report are entered separately, and field comparison is not performed in the node.
- Symptom: the investigation report has been updated, but the expert appraisal opinion still cites the old conclusion. Cause: versions are not synchronized, the old version is not marked invalid, and the branch continues executing based on the old citation.
- Symptom: the receipt or signature column is missing, yet the process has already entered the next stage. Cause: the closing condition is not verified in the branch decision, and the interaction state record does not reflect the missing item.
How to verify the setup
Feature acceptance: run tests on each option one by one, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and record variables and nodeId.
Business test: change one piece of content, see whether the version number and citations are updated synchronously, and check that the current version is unique, old versions are traceable, and citations are synchronized.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and trigger one run to view the node status in the run records.
- Reference the selection result variable in a subsequent node and run a test once, check
variablesandnodeId, and confirm that the process continues downward after the interaction is completed.