What this category's data looks like
This category covers student disciplinary and appeal handling. Materials come from three types: disciplinary fact materials, disciplinary decision documents, and appeal statements. The update cadence advances step by step with the investigation progress, decision issuance, appeal acceptance, and review conclusions. Field characteristics center on the party's name, disciplinary time, behavior description, disciplinary basis, signature, and receipt date. Disciplinary fact materials serve as the original record and, once entering the workflow, act as the version starting point; disciplinary decision documents serve as the conclusion and cite the fact materials while locking the current version; appeal statements serve as the review trigger and carry old-version references and signature status. For the same record, the names, quantities, and dates across the three material types must be consistent. The version number increments with any field change, old versions are retained for traceability, and reference relationships are refreshed synchronously to avoid disconnection between the ledger and external documents.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The version ledger and change records are then completed by subsequent nodes continuing execution along the branch. When a node is triggered, the conversation enters an interactive 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 |
|---|---|---|
| Disciplinary fact materials | The party's name, disciplinary time, behavior description, and quantity are consistent item by item in the disciplinary decision document and appeal statement, and the signature and receipt date are complete | Check the options and branch connections one by one in the node, run a test with references to variables and nodeId, and view the node status in the run records |
| Disciplinary decision document | The disciplinary basis, decision date, delivery signature, and corresponding fields in the fact materials are consistent; the current version is unique and old versions are traceable | Reference the selection result variable in subsequent nodes and run a test, and check whether the version number referenced by the decision document is synchronized with the ledger record |
| Appeal statement | The appellant, appeal date, and requested matters are consistent with the references in the decision document; signatures or receipts are not missing; old-version references already point to the current version | Trigger an interaction, view the node status in the run records, and confirm that the record name, quantity, and date referenced by the appeal statement match the decision document |
| Version ledger and change records | The current version is unique, old versions are traceable, references are synchronized, and change records include field differences and effective dates | Change one piece of content, see whether the version number and references update synchronously, and check the values of variables in subsequent nodes |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the fact materials and the decision document. Cause: The materials are maintained separately, and the reference fields are not refreshed uniformly after node interaction.
- Symptom: The disciplinary decision document has been updated, but the appeal statement still references the old version, and the ledger and external documents are out of sync. Cause: The version was not synchronized, and the branch direction was not re-executed according to the current version.
- Symptom: The decision document or appeal statement lacks a signature or receipt, but the process still continues downward. Cause: The interaction state record did not verify the signature field and receipt date.
How to verify the setup
Feature acceptance: Run tests option by option, check the branch direction and interaction state in the run records, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
Business testing: Change one piece of content, see whether the version number and references update synchronously, and check whether the values of variables and nodeId in the run records are consistent with the branch direction.
- Check the options and branch connections one by one in the node, and after triggering an interaction, view the node status and branch direction in the run records.
- Reference the selection result variable in subsequent nodes and run a test once; after changing one piece of content, check the version number, reference synchronization, and signature and receipt fields.