What this category's data looks like
This category's data covers three types of materials: admission plans, application material checklists, and admission lists. Admission plans come from education authorities and school decision-making meetings, and are updated by academic year or batch; application material checklists come from the admissions working group, and are adjusted with policy and material requirements; admission lists come from the admission review stage, and are archived after being published by batch. When these materials enter the data version and change maintenance function, admission plans play the role of rule basis, application material checklists play the role of operational guidance, and admission lists play the role of result evidence. Field characteristics center on names, quantities, dates, and signature receipts; the update rhythm is synchronized with admission batches, and old versions need to be retained for reference.
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 to complete the rest.
| Object | Check | Verification action |
|---|---|---|
| Admission plan | The name, date, and signature of the same plan do not match across the two materials | Compare the name and date fields in the plan body and the ledger records, and check whether the signature field and receipt are complete |
| Application material checklist | The name and quantity of the same record do not match across the two materials | Check the checklist entries against the ledger quantity fields item by item, and check whether the version number is updated synchronously |
| Admission list | The name, quantity, and date of the same record do not match across the two materials | Compare the name, quantity, and date in the list and the ledger, and confirm that signatures and receipts are not missing |
| HTTP request | Placeholder variables can be resolved into actual values, and the fields are consistent with the external interface agreement | View the full rendered address in the request preview, and check the sources of Authorization, variables, and responseData |
Three common errors
- Symptom: The name and date of the same record do not match between the admission plan and the application material checklist. Cause: The two materials are maintained separately, versions are not synchronized, and old versions are not archived in time.
- Symptom: The quantity and date of the admission list and the ledger are inconsistent. Cause: Only one place is changed during modification, references are not updated synchronously, and the old version is still referenced.
- Symptom: Materials lack signatures or receipts. Cause: The circulation step does not verify the signature field, and receipts are not retained together with the version.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample to confirm that Authorization, variables, and responseData can all be parsed correctly.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- Check the request header names and value sources, and confirm that authentication information is passed in according to the external system's requirements.
- Use one sample request to compare the response, and check whether the request body fields are consistent with the external interface agreement.