What this category's data looks like
This page focuses on data versions and change maintenance in student status changes and graduation qualification review. The source materials include leave-of-absence and return-to-study applications, major transfer applications, graduation review checklists, and the accompanying signatures and receipts. Leave-of-absence and return-to-study applications carry the change start and end dates, change type, and approval signature; major transfer applications carry the transferring-in and transferring-out majors, effective term, and signatures from both parties; graduation review checklists carry course names, credit counts, completion dates, and review conclusions. When the materials enter this function, leave-of-absence and return-to-study applications and major transfer applications serve as change sources, while graduation review checklists serve as the basis for qualification determination; together, the three support the version ledger and change records. The update cadence advances with change approvals and graduation review batches, and the field characteristics are concentrated in four categories: names, quantities, dates, and signatures.
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 "version ledger and change records" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement before continuing. The request URL, path parameters, request headers, and request body can all be populated with variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Leave-of-absence and return-to-study application | Whether the change start and end dates and signature are consistent with the current version | In the request preview, check the fully rendered URL and request body fields, and confirm that the sources of the dates and signature are traceable |
| Major transfer application | Whether the transferring-in and transferring-out major names and effective term match the graduation review checklist | Compare the response with a sample request, and check the source of each placeholder in the variables panel |
| Graduation review checklist | Whether the course names, credit counts, and completion dates are synchronized with the current version | Check the request header names and the sources of their values, and confirm that authentication information is passed in according to the external system's requirements |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, check whether the version number and references are updated in sync, and record the tokens of the referenced text |
Three common errors
- Symptom: The dates for the same record do not match between the leave-of-absence and return-to-study application and the graduation review checklist. Cause: The two materials are maintained separately, and changes are not written back uniformly.
- Symptom: The major transfer application has been updated, but the graduation review checklist still references the old version. Cause: The version was not synchronized, and the reference relationship was not refreshed with the change.
- Symptom: The external system receives empty fields or the request returns 401. Cause: The request body fields are inconsistent with the agreement, or authentication information was not passed in according to the external system's requirements.
How to verify the setup
Function acceptance: preview the rendered request, check the status code and returned fields in responseData, then compare the result against a sample, and check the sources of variables and Authorization in the variables panel.
Business test: change one piece of content and see whether the version number and references are updated in sync.
- In the request preview, check the fully rendered URL and confirm that the path parameter placeholders can be resolved into actual values.
- Compare the response with a sample request, and check that the request body fields are consistent with the external interface agreement.