What this category's data looks like
This page addresses the category of student disciplinary actions and appeals handling. Materials come from three types of documents: disciplinary fact materials, disciplinary decision letters, and appeal letters. The update cadence refreshes link by link as the disciplinary process advances. Disciplinary fact materials provide record name, quantity, date, and signature fields; disciplinary decision letters carry the decision basis and effective date; appeal letters correspond to appeal request and receipt fields. When the three types of materials enter the workflow, each plays a different role: disciplinary fact materials serve as the source of facts, disciplinary decision letters serve as the basis for conclusions, and appeal letters serve as the entry point for relief. Field characteristics center on the consistency of the same record's name, quantity, and date across the three materials, version synchronization status, and the completeness of signatures and receipts. Drafting materials and handover of responsibility require complete fields, clear responsible persons, and consistent versions and dates, ultimately producing a signable material draft and handover record to be signed off by the next stage.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The signable material draft and handover record are completed by subsequent nodes continuing execution according to the branch. When a 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 |
|---|---|---|
| Disciplinary fact materials | Whether the name, quantity, date, and signature are consistent with the disciplinary decision letter and appeal letter | Check the options and branch connections one by one in the node, and compare the same record fields across the three materials |
| Disciplinary decision letter | Whether the version and date are synchronized, and whether the signature and receipt are complete | Trigger a node once and check the node status and branch direction in the run record |
| Appeal letter | Whether the appeal request and receipt fields are complete, and whether the responsible person is clear | Reference variables and nodeId in subsequent nodes and run a test once |
| Handover record | Whether the next stage's sign-off person, sign-off date, and version are consistent | Draft one according to the template and complete one handover, then check whether missing items are blocked |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the disciplinary fact materials and the disciplinary decision letter. Cause: The two materials were drafted separately, and the fields were not checked in the same node.
- Symptom: The version of the disciplinary decision letter is not synchronized, and the appeal letter still references the old version. Cause: After the version update, the interaction state record was not triggered, and the branch did not follow the new version.
- Symptom: The appeal letter lacks a signature or receipt, and the handover record has no sign-off person. Cause: The node did not block missing items, and subsequent nodes directly continued execution along the default branch.
How to verify the setup
Acceptance of this feature: run a test for each option, check the branch direction and interaction state in the run record, and confirm that variables and nodeId have been passed to subsequent nodes.
Business test: draft one according to the template and complete one handover, then see whether missing items are blocked.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger a node once, check the node status in the run record, and confirm that the process continues execution after the interaction is completed.