What this category's data looks like
This page focuses on the enterprise compliance and safety training category. The source materials are of three types: compliance training courseware, safety operating procedures, and exam records. The update cadence is synchronized with training batches and procedure revisions, and the field characteristics center on names, quantities, dates, signatures, and receipts. Compliance training courseware carries the course topic and the scope of trainees; after entering the form input node, its fields are used for the training item and time in the intake record. Safety operating procedures carry the operation steps and version number; after entering, they are used to check the consistency of operation items and versions. Exam records carry scores, dates, and signatures; after entering, they are used to fill in the assessment results and receipts in the follow-up questions. The three types of materials each play the role of information source in intake and missing-item follow-up. The form is responsible for collecting the field values filled in by the user, and subsequent nodes or humans use them to determine missing items and ask follow-up questions.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, and outputs the field values filled in by the user (passed to subsequent nodes after submission). The "intake record and completed follow-up questions" are then completed by subsequent nodes or humans. After triggering, the conversation enters the interaction 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 |
|---|---|---|
| Compliance training courseware | Whether the field names, dates, and signatures are consistent with the safety operating procedures | Check the field names one by one in the node configuration, and reference the formInputResult field in subsequent nodes for a trial run |
| Safety operating procedures | Whether the version number and quantity are synchronized with the exam records | Check the required settings one by one, confirm that the key material fields are marked as required, and use userSelect to select the version |
| Exam records | Whether the scores, dates, and receipt signatures are complete | Reference this field in subsequent nodes and run a trial to confirm that the corresponding field values can be retrieved after submission |
| Form fields | One-to-one correspondence with the material fields to be collected | Check the field names one by one in the node configuration, and check the field mapping of formInputResult and selectResult |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match across two materials. Cause: The form fields are not in one-to-one correspondence with the material fields, so subsequent nodes retrieve misaligned values after submission.
- Symptom: The version is not synchronized, causing the operation steps to conflict with the courseware content. Cause: The required items do not cover the version number, so subsequent nodes cannot determine version differences after submission.
- Symptom: Submission is still possible when a signature or receipt is missing. Cause: Key material fields are not marked as required, so submission is possible even when required items are empty, and the intake record is incomplete.
How to verify the setup
This feature's acceptance: fill it out once and submit, check the field values retrieved by subsequent nodes, and confirm that the formInputResult and selectResult field values are passed correctly.
Business test: submit a question that lacks key information and see whether it asks a follow-up question before answering.
- 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 this field in subsequent nodes and run a trial to confirm that the corresponding field values can be retrieved after submission.