What this category's data looks like
Undergraduate program revision involves three types of materials: program plans, course syllabi, and credit structure tables. Program plans are drafted by departments, course syllabi are written by course teams, and credit structure tables are compiled by academic affairs. Material updates advance with revision batches, and fields include course name, credit count, course start date, signatures, and receipts. When entering the authorized access and external services function, the program plan serves as the main record providing the external entry point, while course syllabi and credit structure tables are opened as associated attachments according to the visibility scope. External services need to verify whether the visitor's identity matches the visibility scope; unauthorized content must not be visible. Material sources are the academic affairs system and department submissions, and the update rhythm is synchronized by semester or revision milestone. Field characteristics include name consistency, quantity consistency, and date consistency, with signatures and receipts serving as the basis for judging completeness.
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 "external entry points and authorization scope" are parsed by subsequent nodes from the response, or handled by the external system according to the agreement to complete the process. The HTTP node is only responsible for sending requests and retrieving results according to the agreement; it does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Program plan | Whether the course name, credit count, course start date, and signature receipt are consistent with the course syllabus and credit structure table | View the rendered address in the request preview, verify the source of variables and the value of Authorization, and compare the names and quantities in the returned fields |
| Course syllabus | Whether the name, quantity, and date of the same course match across the two materials, and whether the versions are synchronized | Use a sample request to compare the response body, and check whether the course fields in responseData are consistent with the original syllabus |
| Credit structure table | Whether the credit structure and dates are consistent with the program plan, and whether signatures or receipts are complete | Verify the request header names and value sources, and check whether the credit counts and dates in the returned fields match |
| Request address and path parameters | Placeholder variables can be resolved into actual values | View the complete rendered address in the request preview, and confirm that the path parameters match the target interface |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match across the two materials. Cause: The program plan and course syllabus are maintained separately, and after revision they are not updated synchronously, resulting in inconsistency between the returned fields and the original documents.
- Symptom: Versions are not synchronized, and the external service returns old content. Cause: After the materials are updated, resubmission is not triggered, and the HTTP node still references old variables or old addresses.
- Symptom: Signatures or receipts are missing, but visitors can still see the content. Cause: The visibility scope judgment does not treat signatures and receipts as completeness conditions, and unauthorized content is returned.
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 a sample; confirm that the source of variables is traceable, that Authorization is passed in according to the external system's requirements, and that the responseData fields are consistent with the agreement.
Business test: access once with a restricted identity and see whether the visibility scope matches the setting.
- In the variable panel, verify the source of each placeholder, and confirm that the variables in the path parameters, request body, and request headers can all be resolved into actual values.
- Use a sample request to compare the response body, and check whether the course name, credit count, date, signature, and receipt are consistent with the program plan, course syllabus, and credit structure table.