What this category's data looks like
This page addresses the enrollment consultation conversion scenario at training institutions, covering three types of materials: enrollment brochures, consultation records, and trial class schedules. Enrollment brochures carry the course name, number of class hours, start date, and seal; consultation records carry the intent level, communication date, and receipt signature; trial class schedules carry the time slot, teacher, and visit confirmation. The material sources are the enrollment system, consultation forms, and class scheduling tables, and the update cadence is triggered by class-term adjustments and policy changes. After entering this feature, the enrollment brochure serves as the external reference baseline, while consultation records and trial class schedules serve as the internal verification basis; the fields of all three must remain currently unique, with old versions traceable and references synchronized in the version ledger.
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 externally by an external system as agreed, and then completed.
| Object | Check | Verification action |
|---|---|---|
| Enrollment brochure | The course name, number of class hours, and start date are consistent across the three materials, and the seal is complete | Check the fully rendered address in the request preview, and compare the brochure fields with the consultation records and trial class schedules |
| Consultation record | The intent level, communication date, and receipt signature have no missing items, and the same record name and quantity match up | Check the request header names and the source of their values, and confirm that the authentication information is passed in according to the external system's requirements |
| Trial class schedule | The time slot, teacher, and visit confirmation dates are consistent between the class scheduling table and the brochure, with no unsynchronized versions | Use a sample request to compare the response, and check that the request body fields match the external interface agreement |
| Variable sources | Every placeholder can be traced to a specific origin, and variables come from global variables, system variables, or the output of preceding nodes | Check the source of each placeholder in the variables panel, and confirm that variables and responseData can be parsed |
Three common errors
- Symptom: The course name and number of class hours for the same record do not match between the brochure and the consultation record. Cause: After changing one piece of content, the reference was not updated synchronously, and the version ledger did not record the change.
- Symptom: The trial class schedule date is inconsistent with the brochure start date, and the old version is still referenced. Cause: The versions are not synchronized, the current version is not unique, and the traceability chain for the old version is broken.
- Symptom: The consultation record lacks a receipt signature, and the trial class schedule lacks visit confirmation. Cause: No signature verification was set up in the material circulation step, and the external system received empty fields.
How to verify the setup
Feature acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that Authorization, variables, and responseData have correct values.
Business test: change one piece of content, see whether the version number and references are updated synchronously, and check whether the fields, dates, and signatures of the three materials—enrollment brochure, consultation records, and trial class schedules—are consistent.
- Check the fully rendered address in the request preview, and confirm that the path parameter placeholders are resolved to actual values.
- Check the source of each placeholder in the variables panel, and confirm that the request header authentication information and request body fields comply with the external interface agreement.