What this category's data looks like
This page centers on the student disciplinary and appeal handling category. The material sources are the school's student affairs department and the appeal acceptance body, and the update cadence keeps pace with the progress of the disciplinary process and the appeal milestones. The materials that enter workflow orchestration include three types: disciplinary fact materials, the disciplinary decision document, and the appeal letter. Disciplinary fact materials play the role of fact determination and evidence chain; the disciplinary decision document plays the role of conclusion and delivery; the appeal letter plays the role of raising objections and triggering review. Field characteristics center on name, quantity, date, and signature: disciplinary fact materials must record the behavior description, the number of people involved, and the date of occurrence; the disciplinary decision document must state the type of disciplinary action, the clauses relied upon, the decision date, and the seal; the appeal letter must state the appellant, the appeal matter, the submission date, and the receipt. When these three types of materials enter the authorized access and external services stage, they respectively correspond to visible-scope determination, external entry opening, and branch direction confirmation.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "External-facing entries and authorization scope" are then completed by subsequent nodes continuing execution along the branches. 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 chosen option.
| Object | Check | Verification action |
|---|---|---|
| Disciplinary fact materials | Whether the name, quantity, date, and signature are consistent with the disciplinary decision document | Compare item by item the behavior description, number of people involved, and date of occurrence in the two materials, and check whether the signature and receipt are complete |
| Disciplinary decision document | Whether the type of disciplinary action, clauses relied upon, decision date, and seal are complete | Check the name and date against the disciplinary fact materials, and check whether the version is in sync and whether the seal is missing |
| Appeal letter | Whether the appellant, appeal matter, submission date, and receipt correspond | Compare the disciplinary action name and date with the disciplinary decision document, and check whether the receipt has been returned and whether the version is consistent |
| User selection node | Whether each option corresponds to one branch, and whether the options and branch connections match one by one | Check the options and branch connections one by one in the node, trigger it once and then view the node status in the run record, and reference variables and nodeId in subsequent nodes for a trial run |
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 document. Cause: The two materials are entered separately, without cross-checking and version synchronization.
- Symptom: The appeal letter lacks a signature or receipt, yet the external entry is still opened along the default branch. Cause: The material circulation step does not validate the signature and receipt fields, and branch determination is not bound to material completeness.
- Symptom: After selecting a certain option, the default branch is still taken, and the process stops after the interaction completes. Cause: The options and branch connections were not checked one by one, the interaction state was not correctly recorded, and the selection result variable was not passed to subsequent nodes.
How to verify the setup
This feature's acceptance: run a trial for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to the correct branch, and reference variables and nodeId in subsequent nodes to verify that the selection result has been passed.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and confirm that unauthorized content is not visible.
- In the user selection node, check the options and branch connections one by one, trigger it once and then view the node status in the run record, and confirm that the interaction state is recorded.
- Reference the selection result variable in a subsequent node and run a trial once, check whether that variable and
nodeIdhave been correctly passed in, and confirm that the branch direction matches expectations.