What this category's data looks like
This page addresses the scenario of pre-departure training and overseas safety reminders. The materials include three types: pre-departure training courseware, safety reminder checklists, and accommodation contact forms. The courseware is updated by the training instructor according to the project cycle, with fields including course name, training date, and instructor signature; the safety reminder checklist is updated by the safety liaison according to the destination risk level, with fields including reminder items, effective date, and receipt signature; the accommodation contact form is updated by the overseas affairs coordinator according to the batch, with fields including accommodation address, contact person, check-in date, and confirmation signature. When the three types of materials enter the form input node, each assumes a field collection role: the courseware provides training record fields, the checklist provides safety reminder and receipt fields, and the contact form provides accommodation and contact person fields. The update rhythm is adjusted according to project batches and destinations. The name and date of the same record in the courseware and the checklist must be consistent, the version number and signature receipt must be synchronized, and missing items are blocked by required markers.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, which outputs the field values filled in by the user (passed to subsequent nodes after submission). "Draft materials that can be issued and handover records" are completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters an interactive state and records the workflow state. After the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | Fields include course name, training date, and instructor signature, and the date is consistent with the record of the same name in the safety reminder checklist | Check the field names one by one in the node configuration, use formInput to reference the fields and run a trial, and confirm that subsequent nodes obtain the courseware field values |
| Safety reminder checklist | Fields include reminder items, effective date, and receipt signature, and the version number is synchronized with the accommodation contact form | Check the required settings one by one, use userSelect to select the destination and submit, and check whether the checklist field values are passed to subsequent nodes |
| Accommodation contact form | Fields include accommodation address, contact person, check-in date, and confirmation signature, and the batch name is consistent with that in the courseware | Reference this field in subsequent nodes and run a trial, check whether the field transfer is complete after submission, and whether missing items are blocked by required markers |
| Handover record | The responsible person is clear, the version and date are consistent, and signatures or receipts are complete | Draft one according to the template and complete one handover, and check whether the handover record fields align with the three materials |
Three common errors
- Phenomenon: The name and date of the same record in the pre-departure training courseware and the safety reminder checklist do not match. Cause: The two materials were drafted separately, and no cross-check of fields was done before submission.
- Phenomenon: The version of the accommodation contact form is not synchronized, and the old address is still referenced. Cause: The version number and effective date were not updated together with the form submission, and subsequent nodes obtained the old values.
- Phenomenon: The safety reminder checklist lacks a signature or receipt, and the handover record is incomplete. Cause: The required markers did not cover the signature and receipt fields, and after submission subsequent nodes could not obtain the corresponding values.
How to verify the setup
Acceptance of this feature: Fill in once and submit, check the field values obtained by subsequent nodes, and confirm that the fields referenced by formInputResult and selectResult are consistent with the submitted content.
Business test: Draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the field names and required markers one by one in the node configuration, and confirm that key material fields are marked as required.
- Reference this field in subsequent nodes and run a trial, confirm that the field transfer is complete after submission, and that the conversation does not remain in the interactive state.