Workflow Orchestration for Training Provider Admissions and Inquiry Follow-Up: Trace Exceptions and Review Results

Training Admissions: review workflows for exception review. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

Training institution enrollment consultation conversion involves three types of materials: enrollment brochures, consultation records, and trial class schedules. Enrollment brochures are published by marketing or academic affairs and contain course names, class types, class hours, pricing basis, and applicable dates; consultation records are registered item by item by consultants and contain source channels, intention levels, communication summaries, follow-up persons, and dates; trial class schedules are generated by the scheduling side and contain trial times, teachers, classrooms, attendance, and receipt status. The three types of materials update at different rhythms: brochures change versions by enrollment period, consultation records are appended with each touchpoint, and trial schedules roll weekly. The materials play different roles when entering the workflow: brochures serve as the basis for standards, consultation records serve as process evidence, and trial schedules serve as fulfillment evidence. Field characteristics are concentrated in names, quantities, dates, version numbers, and signature positions. If any field does not match between two materials, it forms an exception clue to be traced, requiring manual review and a recorded conclusion.

Configuration and implementation checks

This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "exception list and review conclusions" are completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interaction state and records the workflow status. After the user completes the selection, execution continues along the branch corresponding to the selected option. Options and branches must be checked one by one in the node for their connections.

ObjectCheckVerification action
Enrollment brochureWhether the course name, class type, class hours, pricing basis, and applicable dates are consistent with the consultation records; whether the version number is synchronized after a version changeRetrieve the original brochure and compare it field by field with the consultation records, use variables to record differing fields, and use nodeId to locate the node where the difference occurred
Consultation recordWhether the source channel, intention level, follow-up person, date, and signature position are complete; whether the name, quantity, and date in the same record match those in the brochure and trial class scheduleRetrieve the original entries of the consultation records, verify signatures and receipts, write inconsistencies into the exception list, and annotate the source material
Trial class scheduleWhether the trial time, teacher, classroom, attendance, and receipt status are consistent with what the consultation records promised; whether missing signatures or receipts are flaggedCompare against the scheduling table and attendance receipts, use variables to receive the selection result variable, reference it in subsequent nodes, and run a trial once
Exception list and review conclusionsWhether the exception is supported by original records, whether the reviewer has signed, and whether the conclusion can be handed to the responsible person for handlingTrace each item back to the original brochure, consultation record, and trial class schedule, complete the signatures, and archive

Three common errors

  • Symptom: The same student's name and class hours do not match between the consultation record and the trial class schedule. Cause: The two materials are entered separately, and field comparison is not performed using the brochure standards as the basis.
  • Symptom: After the brochure version changes, the consultation record still references the old class type and old date. Cause: The version was not synchronized, and although the materials update at different rhythms, no version verification record was left at the node.
  • Symptom: The trial class schedule lacks an attendance receipt or reviewer signature. Cause: The fulfillment evidence was not collected, and the exception list enters the handling stage without support from original records.

How to verify the setup

Acceptance of this feature: run trials for each option one by one, check the branch directions and interaction status in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and use nodeId to check node status.

Business test: create an exception record and see whether it can be traced to the source materials, that is, trace from the exception list back to the original fields and signatures of the enrollment brochure, consultation record, and trial class schedule.

  • In the user selection node, check the options and branch connections one by one, confirm that no option still follows the default branch, that the process does not stall after the interaction is completed, and that the same session does not repeatedly enter the interaction.
  • For the exception list, check item by item the support from original records and the reviewer's signature, confirm that the conclusion can be handed to the responsible person for handling, and record the number of references and the tokens budget for the referenced text.