What this category's data looks like
This page focuses on the student disciplinary and appeal handling category. The material sources are the school's student affairs department and appeal intake body, and the update cadence advances in sync with the nodes of the disciplinary process. Core materials include the disciplinary fact materials, the disciplinary decision, and the appeal statement. The disciplinary fact materials play the role of factual description and evidence listing, and after entering the workflow are used to identify missing-item questions; the disciplinary decision plays the role of disciplinary basis and decision outcome, and its date and signature fields are used to compare consistency; the appeal statement plays the role of the student's demands and reasons, and after entering the interaction node triggers follow-up questions and branch selection. All three types of materials contain the party's name, quantity, date, signature, and receipt in their field characteristics, and each item must be checked one by one during question-and-answer intake.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting the branch direction and interaction state record. The "intake record and the items to be completed" are continued and completed by subsequent nodes according to the branch. When the node is triggered, the conversation enters the 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, and date are consistent with the disciplinary decision | Compare the party's name and disciplinary quantity in the two materials item by item, mark inconsistencies, and record them |
| Disciplinary decision | Whether the signature and receipt are complete, and whether the date connects with the appeal statement | Check the signature field and receipt copy of the decision, and check whether the date is earlier than the appeal statement submission date |
| Appeal statement | Whether the version is in sync with the intake record, and whether missing items are identified | Check whether the appeal statement version number is consistent with the reference in the intake record, and trigger follow-up questions when key information is missing |
| User selection node | Whether each option corresponds to one branch, and whether the selection result variable is passed | Check the options and branch connections one by one in the node, reference variables in subsequent nodes, and run a trial |
Three common errors
- Phenomenon: The name and quantity of the same disciplinary record do not match between the fact materials and the decision. Cause: The two materials were entered separately, without field-level comparison and synchronization.
- Phenomenon: The appeal statement version is not synchronized, and the intake record references an old version. Cause: After the material was updated, version verification was not triggered, and the workflow continued according to the old version.
- Phenomenon: The disciplinary decision lacks a signature or receipt, but the process still enters the appeal branch. Cause: The interaction node did not treat the missing signature as a follow-up item and let it pass directly.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch direction and interaction state in the run record, and confirm that the node state corresponding to nodeId is recorded and that the selection result variable has been passed to subsequent nodes.
Business test: submit a question missing key information and see whether it asks a follow-up question first before answering.
- Check the options and branch connections one by one in the user selection node, trigger one interaction, and then view the node state and
nodeIdin the run record. - Reference
variablesin a subsequent node and run a trial once to confirm that the selection result variable has been passed and that the branch direction is consistent with the option.