What this category's data looks like
This category involves three types of materials: pre-departure training courseware, safety reminder checklists, and accommodation contact forms. The courseware contains the course name, version number, effective date, revision notes, and instructor signature; the safety reminder checklist contains reminder items, applicable regions, update date, and review signature; the accommodation contact form contains accommodation name, address, contact person, contact phone number, confirmation date, and receipt signature. The materials come from the school's international office, the project team, and overseas partners. The update cadence rolls forward by semester or travel batch, and revisions are made immediately when policies or regional security conditions change. When the three types of materials enter this feature, the courseware and checklist serve as sources of request body fields, while the contact form serves as the query object after path parameters and request header authentication, each carrying the transfer roles of version identifier, date stamp, and signature receipt.
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 completed by subsequent nodes parsing the response, or by an external system handling them according to the agreement. The request URL, path parameters, request headers, and request body can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | Whether the courseware version number, effective date, revision notes, and instructor signature are consistent with the ledger | Use variables as placeholders for the courseware version number and effective date in the request body, compare the returned fields with a sample request, and check the version identifier in responseData |
| Safety reminder checklist | Whether the reminder items, applicable regions, update date, and review signature are consistent with the ledger | Pass Authorization in the request header as required by the external system, check the request header name and the source of its value, and confirm the checklist update date and signature receipt fields |
| Accommodation contact form | Whether the accommodation name, address, contact person, contact phone number, confirmation date, and receipt signature are consistent with the ledger | Use variables as placeholders for the accommodation number and confirmation date in the path parameters and request URL, and check the source of each placeholder in the variable panel |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | Check the correspondence between version numbers and reference fields in variables, and confirm that after changing content in one place, the version number and references are updated synchronously |
Three common errors
- Symptom: The name, quantity, or date of the same accommodation record does not match between the courseware and the contact form. Cause: The two materials are maintained separately and fields are not synchronized using the version ledger as the single source of truth.
- Symptom: The courseware has been revised, but the safety reminder checklist still references old-version items. Cause: The version was not synchronized, the change record did not trigger a reference update, and the old version cannot be traced.
- Symptom: The accommodation contact form lacks a receipt signature or has an empty confirmation date. Cause: The external system received empty fields, or signature information was not backfilled after the request returned 401.
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; check the value sources of the three identifiers Authorization, variables, and responseData.
Business test: change content in one place and see whether the version number and references are updated synchronously.
- In the request preview, view the complete rendered URL and check whether the path parameter placeholders are parsed into actual values.
- In the variable panel, check the source of each placeholder and confirm that the request header name and value source meet the external system's requirements.