What this category's data looks like
This page addresses the scenario of student disciplinary actions and appeal handling. The materials include three types: disciplinary fact materials, disciplinary decision documents, and appeal letters. Disciplinary fact materials are formed by the student affairs or academic affairs department during the investigation stage, recording the time, location, behavioral description, and evidence list of the violation; disciplinary decision documents are issued by the deliberative body, containing the type of disciplinary action, the clauses relied upon, the effective date, and the seal; appeal letters are submitted by students, containing the appeal request, reasons, evidence, and receipt. The three types of materials are summarized weekly, with fields focusing on name, quantity, date, and signature for verification. When materials enter this function, disciplinary fact materials and disciplinary decision documents serve as sources of progress records, and appeal letters serve as sources of status changes. They are pushed to external systems via the HTTP interface respectively, and then subsequent nodes or external systems generate the progress table and statistical scope description as agreed.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The "progress table and statistical scope description" is completed by subsequent nodes parsing the response, or by the external system processing it as agreed. The request URL, path parameters, request headers, and request body can all reference global variables, system variables, or outputs of preceding nodes via variables. 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 correspond item by item with the disciplinary decision document | Check the request body fields against the material fields, and compare the record identifiers in the returned fields |
| Disciplinary decision document | The type of disciplinary action, clauses relied upon, effective date, and seal are complete | Check the request header Authorization and request body fields, and compare the return using a sample request |
| Appeal letter | The appeal request, reasons, evidence, and receipt date are consistent | Check the path parameters and request body fields, and confirm that the status field in responseData is parseable |
| Progress table and statistical scope description | The number of records matches the statistical count, and the scope is written in the header | Use one week of records to verify the totals, and check whether exceptions are stated in the header |
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 field-level comparison and version synchronization.
- Symptom: The appeal letter lacks a signature or receipt, but the progress record still shows it as accepted. Cause: The receipt field is not included in the request body validation, and the external system processes it as an empty field.
- Symptom: The request returns 401 or times out, and the progress table is missing rows. Cause: The source of the
Authorizationvalue is incorrect, or the variable is not resolved to an actual value.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample, confirming that the record identifiers in responseData are consistent with the materials.
Business testing: Use one week of records to verify the totals, check whether the scope and exceptions are clearly stated, and whether the number of records matches the statistical count.
- In the variables panel, check the source of each placeholder, confirming that
variablescan be traced to global variables, system variables, or outputs of preceding nodes. - Check the request header names and value sources, and use a sample request to compare the returned fields with the material fields.