What this category's data looks like
Student disciplinary and appeal handling materials include three types: disciplinary fact materials, disciplinary decision documents, and appeal statements. Disciplinary fact materials are compiled by counselors or student affairs departments within one week after the incident, containing fact descriptions, dates, and signatures of the parties involved; disciplinary decision documents are produced by the college after fact determination, containing the type of disciplinary action, the clauses based on which the decision is made, and delivery receipts; appeal statements are submitted by students or their representatives, containing appeal requests, reasons, evidence lists, and receipt dates. After the three types of materials enter the workflow, their roles differ: disciplinary fact materials serve as the starting point of the record, disciplinary decision documents serve as the result evidence, and appeal statements serve as the trigger condition for review. The update rhythm is weekly summary and monthly archiving, with fields mainly including name, student ID, incident date, disciplinary document number, and appeal status.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "progress table and statistical scope description" is completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Disciplinary fact materials | Check whether the fields include name, student ID, incident date, and signature; whether the date is consistent with the disciplinary decision document | In the node, check the options and branch connections one by one, and reference variables to see whether the branch corresponding to this material is selected |
| Disciplinary decision document | Check whether the disciplinary document number, disciplinary type, and delivery receipt are complete; whether the name, quantity, and date match those in the disciplinary fact materials | Trigger a user selection node once, and in the run record check the interaction status and branch direction corresponding to nodeId |
| Appeal statement | Check whether the appeal request, reasons, evidence list, and receipt date are complete; whether the document number and date are consistent with the disciplinary decision document | In subsequent nodes, reference the selection result variable and run a trial once, and check the status record after this material enters the review branch |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the disciplinary fact materials and the disciplinary decision document. Cause: The two materials are entered separately, without field-level verification and version synchronization.
- Phenomenon: The disciplinary decision document lacks a signature or delivery receipt, and the appeal statement lacks a receipt date. Cause: No required-field validation is set in the material circulation step, and the node branches do not cover missing-document situations.
- Phenomenon: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked item by item, and the selection result variable was not correctly referenced.
How to verify the setup
Acceptance of this function: Run trials for each option one by one, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, and in subsequent nodes reference variables and nodeId to check whether the selection result variable has been passed.
Business test: Use one week of records to check the totals, see whether the scope and exceptions are clearly stated, and confirm that the number of records matches the statistical number and that the scope is written in the header.
- In the node, check the options and branch connections one by one to ensure that each option corresponds to one branch, and run a trial once to view the interaction status record.
- In subsequent nodes, reference the selection result variable and run a trial once to check whether the name, quantity, date, and signature receipt of the same record are consistent across the disciplinary fact materials, disciplinary decision document, and appeal statement.