What this category's data looks like
This page is for student disciplinary and appeal handling scenarios, focusing on the data versions and change maintenance of three categories of materials: disciplinary fact materials, disciplinary decision documents, and appeal statements. Disciplinary fact materials record the course of conduct, time and place, and evidence list; disciplinary decision documents carry the disciplinary basis, decision content, effective date, and signatures and seals; appeal statements include the appeal request, factual reasons, submission date, and receipt information. The three types of materials are produced in batches at each stage of submission, delivery, archiving, and review, and the update rhythm is driven by disciplinary process nodes. When materials enter the HTTP interface and external system functions, each assumes a different role: disciplinary fact materials serve as the factual draft for comparison, disciplinary decision documents serve as the master record of the current version, and appeal statements serve as procedural receipt evidence. Field characteristics are concentrated in names, quantities, dates, signatures, and receipt numbers, and any change in any one of them requires synchronizing the version ledger and reference locations.
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 version ledger and change records are parsed from the response by subsequent nodes, or handled by an external system according to the agreement and then completed. The HTTP module sends a request to the target address, and variables can be used as placeholders in all three places: path parameters, request body, and request headers. Variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Disciplinary fact materials | Names, quantities, dates, and signatures must be consistent with the disciplinary decision document | Take one record, compare the names, quantities, dates, and signature fields in the two materials, and check the placeholder source of variables |
| Disciplinary decision document | The current version is unique, old versions are traceable, and references are synchronized | In the version ledger, confirm that the current version number is unique, and check whether the old version archive and reference locations are updated synchronously |
| Appeal statement | The appeal request, date, and receipt information are complete | Check the appeal statement submission date, receipt number, and signature, and confirm that the fields returned by responseData are consistent with the agreement |
| Request headers and request body | Authentication information is consistent with the field agreement | Check the source of the Authorization request header value, and use one sample request to compare the returned fields |
Three common errors
- Symptom: The names, quantities, and dates of the same record do not match between the disciplinary fact materials and the disciplinary decision document. Cause: The two materials were entered separately, and field comparison was not performed based on the current version.
- Symptom: The disciplinary decision document has been updated, but the knowledge base or external documents still reference the old version. Cause: The version ledger was not synchronized, and the reference locations were not updated when the version number changed.
- Symptom: The appeal statement lacks a signature or receipt number. Cause: The submission step did not validate the signature and receipt fields, and subsequent nodes did not intercept empty fields when parsing the response.
How to verify the setup
Acceptance for this feature: preview the rendered request, check the status code and returned fields, then compare the result against one sample to confirm that the values of variables and responseData are correct.
Business test: change one piece of content and see whether the version number and references are updated synchronously
- In the variables panel, check the source of each placeholder and confirm that the variables in the request address, request headers, and request body can be resolved into actual values.
- Use one sample request to compare the returned fields, and check that the current version is unique, old versions are traceable, and references are synchronized.