What this category's data looks like
This page addresses the pre-departure training and overseas safety reminder category. Source materials include pre-departure training courseware, safety reminder checklists, and accommodation contact sheets, with an update cadence of weekly aggregation and monthly verification. The courseware records training sessions, dates, and attendee signatures; the safety reminder checklist records reminder items, send dates, and acknowledgments; the accommodation contact sheet records accommodation addresses, contacts, confirmation dates, and signatures. When these three types of materials enter the progress record and statistical verification function, the courseware and checklist serve as sources of progress entries, and the accommodation contact sheet serves as the verification baseline, jointly supporting alignment between recorded counts and statistical counts. In terms of field characteristics, the name, quantity, and date of the same record must be consistent across the three materials, versions must be synchronized, and signatures or acknowledgments must be complete.
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 scope description" is parsed from the response by subsequent nodes, or handled externally by an external system according to the agreement.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | Whether fields, dates, and signatures are consistent with the safety reminder checklist and accommodation contact sheet | Verify the training dates, attendee counts, and signatures in the courseware, and compare them item by item with the checklist and contact sheet |
| Safety reminder checklist | Whether item names, quantities, send dates, and acknowledgments match the courseware and contact sheet | Check the checklist items and acknowledgments, confirm there are no missing signatures or acknowledgments, and verify version synchronization |
| Accommodation contact sheet | Whether accommodation addresses, contacts, confirmation dates, and signatures are consistent with the courseware and checklist | Compare names and dates in the contact sheet with the courseware and checklist, and flag inconsistent items |
| Request URL and path parameters | Placeholder variables can be resolved into actual values | View the full rendered URL in the request preview, and verify the source of variables |
Three common errors
- Symptom: the name and quantity of the same record do not match between the courseware and the checklist. Cause: the two materials are maintained separately and are not updated in sync under a unified scope.
- Symptom: the safety reminder checklist is missing acknowledgments or the accommodation contact sheet is missing signatures. Cause: the sending and confirmation steps are not closed-loop, and acknowledgments and signatures are not collected in time.
- Symptom: the request returns 401 or the external system receives empty fields. Cause:
Authorizationis not passed in as required by the external system, or thevariablesplaceholders are not resolved.
How to verify the setup
This feature's acceptance: preview the rendered request, verify the status code and returned fields, then compare the result against one sample to confirm that the value sources of responseData and Authorization are correct.
Business test: verify totals using one week of records, and check whether the scope and exceptions are clearly stated.
- In the variables panel, verify the source of each placeholder and confirm that
variablescan be traced to global variables, system variables, or outputs of preceding nodes. - Compare the response using one sample request, check that the request body fields are consistent with the external interface agreement, and record the array item count and referenced text tokens.