What this category's data looks like
Pre-departure training and overseas safety reminder materials fall into three categories: pre-departure training courseware, safety reminder checklists, and accommodation contact forms. Courseware is usually updated by batch and includes the training date and instructor signature; safety reminder checklists are maintained by country or region and include the reminder date and person-in-charge confirmation; accommodation contact forms include the accommodation name, address, contact person, check-in date, and receipt signature. When the three categories of materials enter the exception tracing and manual review function, the courseware and checklists serve as the source comparison basis, and the contact forms serve as the receipt verification object, each taking on the role of checking fields, dates, and signatures. The update rhythm uses batches and countries as clues. If the name, quantity, or date of the same record does not match across two materials, or if the version is not synchronized, or a signature or receipt is missing, an exception list is formed.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The "exception list and review conclusion" is completed by subsequent nodes parsing the response, or by an external system handling it as agreed. The HTTP module sends a request to the target address. Path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | Whether the fields, dates, and signatures are consistent with the safety reminder checklist | Check whether the training date and instructor signature in the courseware match the reminder date and person-in-charge confirmation in the checklist; in the variables panel, check the source of each placeholder and confirm that variables can resolve to the courseware fields |
| Safety reminder checklist | Whether the name, quantity, and date of the same record are consistent across the two materials | Use a sample request to compare the return and check whether the reminder name and quantity in the checklist are consistent with the courseware record; in the request preview, view the full rendered address and confirm that the fields returned by responseData correspond to the checklist fields |
| Accommodation contact form | Whether the receipt signature and check-in date are complete | Check the accommodation name, check-in date, and receipt signature in the contact form; if the signature or receipt is missing, record an exception; check the request header names and value sources, and confirm that Authorization is passed in according to the external system's requirements |
| Exception list and review conclusion | Exceptions are supported by original records and signed by the reviewer | Compare the exception records one by one with the source materials and confirm that each exception can be traced to specific fields and dates in the courseware, checklist, or contact form; the review conclusion must have the reviewer's signature |
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 maintained separately, and no cross-check was performed during updates, resulting in differences in field values.
- Symptom: The accommodation contact form version is not synchronized, and the old receipt is still in circulation. Cause: After the materials were updated, they were not uniformly replaced, and the accommodation name and check-in date differ between the old and new versions.
- Symptom: The safety reminder checklist lacks a signature or receipt, and the exception cannot be traced. Cause: The confirmation step left no trace, so during review no original record can be found for support, and the conclusion cannot be signed.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against a sample; confirm that variables, responseData, and Authorization appear in the request as agreed, and that the returned fields are consistent with the exception list fields.
Business test: create an exception record, see whether it can be traced to the source materials, and check whether the fields, dates, and signatures in the courseware, checklist, and contact form can be matched one by one.
- In the variables panel, check the source of each placeholder and confirm that global variables, system variables, and the output of preceding nodes can resolve to actual values.
- Use a sample request to compare the return, check that the request body fields are consistent with the external interface agreement, and that the request header authentication information is passed in according to the external system's requirements.