What this category's data looks like
In the pre-departure training and overseas safety reminders category, the external entry points often include three types of materials: pre-departure training courseware, safety reminder checklists, and accommodation contact forms. Courseware comes from the training department and is updated by semester; safety reminder checklists come from the overseas affairs team and are adjusted by destination and quarter; accommodation contact forms are submitted by overseas liaisons and change with check-in arrangements. When the three types of materials enter the form input node, their roles differ: courseware and checklists serve as the basis for the authorization scope, while accommodation contact forms serve as the source of receipt fields. Field characteristics center on name, material name, date, quantity, signature or receipt. The same record often has mismatched names, quantities, and dates across two materials, versions are not synchronized, and signatures or receipts are missing. After materials enter this feature, only the fields needed to match the visitor's identity and visible scope are collected, and unauthorized content is not visible.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, and it outputs the field values filled in by the user (passed to subsequent nodes after submission). The externally available entry points and authorization scope are then 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 | Check against the safety reminder checklist whether the name, date, and quantity of the same material are consistent | Check the field names one by one in the node configuration, and check whether the required markers cover the key material fields; reference the formInputResult field in subsequent nodes and run a trial |
| Safety reminder checklist | Check against the accommodation contact form whether the date, signature, or receipt is complete and the versions are synchronized | Submit once with a restricted identity, reference the formInputResult field in subsequent nodes and run a trial, and confirm that the value can be retrieved |
| Accommodation contact form | Check against the courseware whether the name, quantity, and date of the same record match | Reference the formInputResult field in subsequent nodes and run a trial, and check whether the subsequent nodes can retrieve the corresponding field value after submission |
| Form input node | Required items cannot be submitted when empty, and after submission the conversation does not remain in the interactive state | Check the required settings one by one, and confirm that the field values can be passed to subsequent nodes after submission; use userSelect to select a restricted identity and run a trial once |
Three common errors
- Symptom: The material names and dates in the same pre-departure training courseware and safety reminder checklist do not match. Cause: The two materials are maintained separately, no cross-check of the same record is performed, and versions are not synchronized.
- Symptom: The accommodation contact form lacks a signature or receipt but is still used as the basis for an externally available entry point. Cause: Key material fields are not marked as required, and empty values are not blocked on submission.
- Symptom: After submission, subsequent nodes cannot retrieve the field values, and the conversation remains in the interactive state. Cause: The field names in the node configuration are inconsistent with subsequent references, or required items can still be submitted when empty.
How to verify the setup
Acceptance for this feature: fill in once and submit, and check the field values retrieved by subsequent nodes; check the field names one by one in the node configuration, confirm that the required markers cover the key material fields, and reference the formInputResult field in subsequent nodes and run a trial to check whether the corresponding field values can be retrieved after submission.
Business test: access once with a restricted identity and see whether the visible scope matches the settings, with unauthorized content not visible; when opening it to parents or superiors, confirm that the entry point and authorization scope match the visitor's identity, and use userSelect to select a restricted identity and run it again once.
- Check the field names and required settings one by one in the node configuration to ensure that key material fields are marked as required.
- Reference the
formInputResultfield in subsequent nodes and run a trial to confirm that the corresponding field values can be retrieved after submission and that the conversation does not get stuck in the interactive state.