What this category's data looks like
This page addresses the category of student disciplinary actions and appeal handling. Materials come from three types of documents: disciplinary fact materials, disciplinary decision letters, and appeal letters, which enter the question intake and missing-item follow-up function one by one at the intake node. Disciplinary fact materials provide behavior descriptions, time and place, and evidence lists; disciplinary decision letters provide the type of disciplinary action, the clauses relied upon, and the effective date; appeal letters provide appeal requests, reasons, and signed receipts. In the function, the three types of materials respectively play the roles of factual source, decision basis, and appeal claim, and their field characteristics center on four comparable items: name, quantity, date, and signature. The update rhythm advances with the disciplinary process; materials from each stage, from notice of proposed disciplinary action to appeal intake, flow in successively, and the field consistency of the same record across the materials must be maintained.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The "intake record and completed question items" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the process. The request URL, path parameters, request headers, and request body can all reference global variables, system variables, or outputs from preceding nodes via variables, and authentication information is placed in Authorization according to the external system's requirements.
| Object | Check | Verification action |
|---|---|---|
| Disciplinary fact materials | Name, quantity, date, and signature must correspond item by item with the disciplinary decision letter; a missing signature or receipt is a missing item | Check the placeholder sources in the variables panel, and use a sample request to compare the returned fields with the material fields |
| Disciplinary decision letter | The type of disciplinary action, the clauses relied upon, and the effective date must be consistent with the facts stated in the appeal letter; if the version is not synchronized, it is a missing item | Preview the rendered request, and check whether the decision letter fields in responseData and the appeal letter fields come from the same source |
| Appeal letter | The appeal request, reasons, and signed receipt must be complete; when key information is missing, ask a follow-up question first before answering | Submit a question missing key information, and observe whether it asks a follow-up question first before answering |
| HTTP request | The placeholder variables in the path parameters, request headers, and request body can be resolved into actual values | Check the request header names and value sources, and confirm that Authorization is passed in according to the external system's requirements |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the disciplinary fact materials and the disciplinary decision letter. Cause: The two materials were entered separately, and no field-level comparison was performed.
- Symptom: After the disciplinary decision letter version is updated, the appeal letter still references the old clauses. Cause: The version was not synchronized, and the placeholder variable retrieved the old output from a preceding node.
- Symptom: The appeal letter lacks a signature or receipt, but the intake record is still generated. Cause: Missing-item identification did not cover the signature field, so no follow-up question was triggered.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that the intake record and completed question item fields in responseData are complete.
Business test: submit a question missing key information, and see whether it asks a follow-up question first before answering.
- Check the source of each placeholder in the variables panel, and confirm that
variablescan be traced to a global variable, system variable, or output from a preceding node. - Use a sample request to compare the return, check that the request body fields are consistent with the external interface agreement, and record the returned fields and status code.