What this category's data looks like
This category's data consists of three types of materials: course offering plans, scheduling tables, and course selection rules. The sources are the academic affairs system and manually confirmed documents, and the update cadence advances by semester and by round. Course offering plans list course names, classes, and capacities; scheduling tables record class dates, periods, and classroom numbers; course selection rules specify the open audience and the selectable scope. When these three types of materials enter the HTTP interface and external system feature, they respectively serve as the source of request body fields, the basis for path parameter values, and the basis for determining the authorization scope. In terms of field characteristics, the names, quantities, and dates of the same course in the two materials must be aligned item by item, and the version is based on the latest signature or receipt. The external entry point and authorization scope are output by this feature, and the visitor identity and visible scope must match; unauthorized access must not be visible.
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 external entry point and authorization scope are parsed from the response by subsequent nodes, or handled by the external system according to the agreement. The HTTP node 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 |
|---|---|---|
| Course offering plan | The course name, class, and capacity must be consistent between the plan and the scheduling table, and the date and signature must be complete | In the request preview, check the rendered complete address and request body fields, and compare the course names and quantities in the two materials |
| Scheduling table | The class date, period, and classroom number must be aligned between the scheduling table and the course selection rules, the versions must be synchronized, and there must be a receipt | Check the request header names and value sources, and confirm that Authorization is passed in according to the external system's requirements |
| Course selection rules | The open audience and selectable scope must match the visitor identity; unauthorized access must not be visible | In the variables panel, check the source of each placeholder, and confirm that variables and responseData can be traced to specific origins |
| HTTP node output | The response body, status code, and returned fields must be consistent with the external interface agreement | Use one sample request to compare the return, and check whether the returned fields contain null values or are missing |
Three common errors
- Symptom: the request returns 401. Cause: the authentication information was not placed in the request header according to the external system's requirements, or the
Authorizationvalue source points to an expired variable. - Symptom: the name, quantity, or date of the same course does not match between the course offering plan and the scheduling table. Cause: the versions of the two materials are not synchronized, and the signature or receipt is missing.
- Symptom: the external system receives empty fields. Cause: the request body fields are inconsistent with the external interface agreement, or the
variablesplaceholders were not parsed into actual values.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample to confirm that responseData is consistent with the agreement.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and confirm that unauthorized access is not visible.
- In the request preview, view the rendered complete address, and check whether the path parameters and request body fields are consistent with the course offering plan and scheduling table.
- Check the request header names and value sources, confirm that the authentication information is passed in according to the external system's requirements, and check the origin of each placeholder in the variables panel.