What this category's data looks like
The data for this category looks like this: Training institution enrollment consultation conversion involves three types of materials: enrollment brochures, consultation records, and trial class schedules. Enrollment brochures are provided by marketing or academic affairs and contain course names, class types, dates, and signatures/seals; consultation records are registered one by one by consultants and contain student names, intended courses, contact information, and follow-up dates; trial class schedules are arranged by academic affairs and contain trial class times, instructors, sign-ins, and receipts. Materials are summarized weekly and archived monthly. Field names and quantities must remain consistent across brochures, records, and schedules, and signatures and receipts are indispensable. When entering the progress record and statistical verification function, brochures serve as the source of definitions, consultation records as the source of details, and trial class schedules as the source of exceptions and write-offs. Together, the three support the generation of the progress table and the statistical definition statement.
Configuration and implementation checks
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 "progress table and statistical definition statement" is parsed from the response by subsequent nodes, or handled externally according to the agreement to complete the process.
| Object | Check | Verification action |
|---|---|---|
| Enrollment brochure | Course names, class types, dates, and signatures/seals are consistent across materials | Compare the brochure and consultation records field by field, checking names, quantities, dates, and signatures |
| Consultation records | The names, quantities, and dates of the same record match between the brochure and the trial class schedule | Sort by student and date, and spot-check three records to verify fields and receipts |
| Trial class schedule | Trial class times, instructors, sign-ins, and receipts are complete and version-synchronized | Check the schedule version number and sign-in receipts, confirming no missing signatures |
| HTTP node | The request URL, request headers, and request body are passed in according to the external interface agreement | View the fully rendered URL in the request preview, and verify the sources of Authorization and variables |
Three common errors
- Symptom: The names, quantities, and dates of the same student do not match between the consultation record and the trial class schedule. Cause: The two materials are registered separately, and fields are not checked against a unified definition.
- Symptom: After the brochure version is updated, the consultation record still references the old class type and old date. Cause: The version is not synchronized, and there is no comparison step between materials.
- Symptom: The trial class schedule lacks sign-ins or receipts, and the progress table cannot confirm exceptions. Cause: Signatures and receipts are not archived with the records, and the statistical definition is not written in the header.
How to verify the setup
Acceptance of this function: Preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that the values of responseData and variables are consistent.
Business test: Use one week of records to verify the totals, check whether the definitions and exceptions are clearly stated, and confirm that the record count matches the statistical count.
- In the variables panel, verify the source of each placeholder, and confirm that
Authorizationandvariablescan be traced to specific origins. - Use a sample request to compare the response, verify that the request body fields are consistent with the external interface agreement, and avoid the external system receiving empty fields.