What this category's data looks like
Materials in the pre-departure training and overseas safety reminders category come from pre-departure training courseware, safety reminder checklists, and accommodation contact forms; the update cadence follows semester batches and destination adjustments, and fields include student name, ID number, date, signature, receipt, and quantity. The courseware handles terminology and translated-name cross-references, the safety reminder checklist handles risk points and emergency wording, and the accommodation contact form handles addresses, contacts, dates, and signed receipts. When these three types of materials enter workflow orchestration, the courseware provides the source terms for the unified terminology glossary and cross-reference draft, the safety reminder checklist provides multilingual versions of safety items, and the accommodation contact form provides field-level cross-references and signed receipt requirements, after which subsequent nodes continue execution by branch.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "unified terminology glossary and cross-reference draft" is then completed by subsequent nodes continuing execution by branch.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | The same term is consistent throughout, translated names can be traced back to the source text, and dates and signatures are complete | Check options and branch connections one by one in the node, and view node status in the run records |
| Safety reminder checklist | When the name, quantity, or date of the same record does not match across the two materials, roll back by branch to verify | Reference the selection result variable in a subsequent node and run a test once to confirm the branch direction |
| Accommodation contact form | When the version is not synchronized or signatures or receipts are missing, enter the correction path by branch | Check options and branch connections to confirm that the process continues after the interaction is completed and does not stall |
| Unified terminology glossary and cross-reference draft | The same term is consistent throughout, translated names can be traced back to the source text; sample three terms and check their usage throughout | Reference variables and nodeId in a subsequent node, and run a test once to confirm the selection result has been passed in |
Three common errors
- Symptom: the name, quantity, or date of the same record does not match across the two materials. Cause: the courseware and the safety reminder checklist are maintained separately and do not uniformly trace back to the source text by branch.
- Symptom: the version is not synchronized, and the old accommodation contact form is still referenced. Cause: after the interaction is completed, execution does not continue by branch, and the node status is not recorded.
- Symptom: signatures or receipts are missing and are only discovered before release. Cause: options and branch connections are not checked one by one, and subsequent nodes do not reference the selection result.
How to verify the setup
Acceptance for this feature: run a test for each option one by one, check the branch direction and interaction state in the run records, confirm that it enters the interaction state and records it, and after selection continue execution by branch according to the corresponding option.
Business test: sample three terms and check whether their usage is consistent throughout, and verify that translated names can be traced back to the source text.
- Check options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference the selection result variable in a subsequent node and run a test once to confirm that
variablesandnodeIdhave been passed in.