What this category's data looks like
In the scenario of investigating and handling academic misconduct reports, the materials that enter the workflow include report materials, investigation reports, and expert appraisal opinions. Report materials usually come from named or anonymous channels and include original records, images, emails, experimental data, etc., and their update cadence changes with supplementary materials. Investigation reports are written by the investigation team and include the accused person's information, timeline, evidence list, and conclusion recommendations, with fields such as name, quantity, date, and signature. Expert appraisal opinions are issued by external experts and include appraisal matters, basis, conclusions, expert signature, and date. After these three types of materials enter this feature, report materials serve as source materials for tracing, investigation reports serve as process records for comparison, and expert appraisal opinions serve as professional judgments for review. Field characteristics are concentrated in name, quantity, date, signature, and receipt, and version synchronization and signature completeness are the key points of verification.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "anomaly list and review conclusions" are then 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.
| Object | Check | Verification action |
|---|---|---|
| Report materials | Whether the name, quantity, and date are consistent with the investigation report, and whether the signature and receipt are complete | Check the options and branch connections one by one in the node, reference variables to record the source, and trigger one check of the node status in the run records |
| Investigation report | Whether the name, quantity, and date of the same record match across the two materials, and whether the versions are synchronized | Reference the selection result variable in a subsequent node and run a trial once, use nodeId to locate the node, and check the signature and receipt |
| Expert appraisal opinions | Whether the appraisal matters, basis, and conclusions correspond to the report materials and investigation report, and whether the expert signature and date are complete | Check the options and branch connections one by one in the node, use variables to record the appraisal opinion reference, and view the node status in the run records |
| Anomaly list and review conclusions | Whether the anomaly is supported by original records, and whether the reviewer has signed | Reference the selection result variable in a subsequent node and run a trial once, use nodeId to locate the node, and check the branch direction and interaction state records |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the report materials and the investigation report. Cause: The two materials were filled in by different personnel at different times, without cross-comparison and unified numbering.
- Phenomenon: The investigation report version is not synchronized, and the expert appraisal opinion cites the conclusion of an old version. Cause: After the version update, the review node was not notified, and subsequent nodes still reference the old version of the materials.
- Phenomenon: The report materials lack a receipt, and the investigation report lacks a signature. Cause: No signature and receipt verification points were set up in the material circulation step, and the node did not record the interaction state.
How to verify the setup
Feature acceptance: run trials option by option, 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 locate it using variables and nodeId.
Business testing: create an anomaly record, see whether it can be traced back to the source materials, and check whether the anomaly list and review conclusions are supported by original records and whether the reviewer has signed.
- Check the options and branch connections one by one in the node, trigger one check of the node status in the run records, and confirm that the process continues after the interaction is completed.
- Reference the selection result variable in a subsequent node and run a trial once, use
nodeIdto locate the node, and check the branch direction and interaction state records.