What this category's data looks like
In the pre-departure training and overseas safety reminders category, materials mainly consist of pre-departure training courseware, safety reminder checklists, and accommodation contact forms. The courseware contains module topics, class hours, and instructor signatures; the checklist contains risk items, handling steps, and version dates; the contact form contains accommodation name, contact person, phone number, and receipt signature. Materials are updated by semester or batch. The name, quantity, and date of the same record in different materials must be consistent, versions must be synchronized, and signatures or receipts must be complete. When entering this function, the courseware is used to locate the training basis, the checklist is used to verify safety items, and the contact form is used to verify accommodation and receipt fields. Each of the three serves as a source of basis and does not replace one another.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch direction and interaction status records. Basis items that can be traced back to the original text must be continued by subsequent nodes according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | Whether the courseware fields, dates, and signatures are consistent with the current version, and whether items can be traced back to the original text | In the node, check the options and branch connections, and trigger one run to view the node status in the run record |
| Safety reminder checklist | Whether the checklist fields, version date, and signature or receipt are complete, and whether the name and quantity of the same record match | In subsequent nodes, reference the selection result variable and run a test once to check whether the variable has been passed to subsequent nodes |
| Accommodation contact form | Whether the contact form fields, dates, and signatures are consistent with the checklist and courseware, and whether items can be traced back to the original text | Check the options and branch connections one by one, and view the status corresponding to nodeId in the run record |
| User selection node | Whether each option corresponds to one branch, and whether the interaction status is recorded | Trigger once, check the branch direction and interaction status in the run record, and inspect the variables reference |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the courseware and the checklist. Cause: The two materials are updated separately, without cross-material field comparison and unification.
- Symptom: The checklist version is not synchronized, and old-version items are still referenced. Cause: The version date was not updated with the batch, and the node branch still points to the old material.
- Symptom: The contact form lacks a signature or receipt, and the basis item cannot be traced back to the original text. Cause: The signature and receipt fields were not verified as complete before entering the process.
How to verify the setup
Acceptance for this function: run each option one by one, and check the branch direction and interaction status in the run record.
Business test: ask a cross-material basis question and see whether the answer provides a traceable source.
- In the node, check the options and branch connections one by one, and confirm that each option corresponds to one branch.
- Trigger one user selection, view the node status and
nodeIdin the run record, and check whethervariableshas been passed to subsequent nodes.