What this category's data looks like
Materials in the pre-departure training and overseas safety reminders category include pre-departure training courseware and safety reminder checklists. The courseware source is finalized by the training department, updated by semester, and contains course modules, teaching dates, and instructor signatures; the safety reminder checklist source is the overseas affairs team, updated by destination and quarter, and contains risk items, emergency phone numbers, and a receipt column; the accommodation contact form source is logistics and overseas counterparts, updated by batch, and contains accommodation name, address, check-in date, and student signature. The three types of materials have different roles when entering the workflow: the courseware and checklist serve as the basis for intake questions, and the accommodation contact form serves as the field comparison worksheet. The update cadence is often not synchronized, and the name, quantity, and date of the same record in the two materials may not match; when a signature or receipt is missing, follow-up questions must be asked first before transferring to the handler.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. The "intake record and completed questions" are continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters the interaction state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | Whether the course modules, teaching dates, and instructor signatures in the courseware are complete, and whether they are consistent with the name, quantity, and date in the safety reminder checklist | Check the options and branch connections one by one in the node, reference variables to record the courseware fields, and trigger once to view the node status in the run record |
| Safety reminder checklist | Whether the risk items, emergency phone numbers, and receipt column are complete, whether the version is synchronized with the courseware, and whether the follow-up branch is triggered when a signature or receipt is missing | Reference nodeId and the selection result variable in subsequent nodes and run a trial once, and check whether the date and quantity of this checklist match those of the accommodation contact form |
| Accommodation contact form | Whether the accommodation name, address, check-in date, and student signature are consistent with the courseware and checklist, and whether the name, quantity, and date of the same record in the two materials do not match | Check the options and branch connections one by one in the node, verify the accommodation fields and selection result variable in variables, and trigger once to view the interaction status |
| Intake record and completed questions | Whether missing items are identified and followed up, whether the answers have material basis, and whether they are transferred to the handler | Reference nodeId in subsequent nodes and run a trial, check the branch direction and interaction status in the run record, and confirm that execution continues after the follow-up |
Three common errors
- Symptom: the name, quantity, and date of the same record in the courseware and safety reminder checklist do not match. Cause: the two material versions are not synchronized, the update cadence differs, and the fields have not been cross-checked.
- Symptom: the accommodation contact form is missing a student signature or the receipt column is blank. Cause: no signature validation is set up in the material collection step, and missing items are not identified and followed up when entering the workflow.
- Symptom: after selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: the options and branch connections have not been checked one by one, and the selection result variable has not been passed to subsequent nodes.
How to verify the setup
Acceptance of this feature: run a trial for each option one by one, check the branch direction and interaction status in the run record, confirm that the selection result variable has been passed to subsequent nodes, and record with reference to variables and nodeId.
Business test: submit a question missing key information, see whether it asks follow-up questions first before answering, and after the answer has material basis, transfer it to the handler.
- Check the options and branch connections one by one in the node, and trigger once to view the node status in the run record.
- Reference the selection result variable and
nodeIdin subsequent nodes and run a trial once, and check the material fields, dates, and signatures.