What this category's data looks like
Enterprise compliance and safety training materials usually consist of three types: compliance training courseware, safety operating procedures, and exam records. Courseware comes from policy documents and position risk lists, operating procedures come from equipment and work standards, and exam records come from the assessment step after training. In terms of update cadence, courseware and procedures are revised as regulations and processes change, while exam records are generated by batch. When materials enter the forms and interaction stage, their roles differ: courseware and procedures are drafts to be drafted, and exam records are vouchers that need to be checked during handover. Field characteristics center on name, quantity, date, signature, and version number, and these fields must be consistent across the two tables of drafting and handover.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, outputting the field values filled in by the user (passed to subsequent nodes after submission). The issuable material drafts and handover records are completed by subsequent nodes or manually afterward. After the form input node is triggered, 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 | Fields complete: courseware name, version number, applicable position, preparation date, signature column, and receipt column must all correspond one-to-one in the form fields | Check the field names one by one in the node configuration, and confirm that key fields are marked as required |
| Safety operating procedures | Date and signature: preparation date, effective date, approval signature, and recipient signature must be consistent with the handover record | Reference this field in a subsequent node and run a test, and check the field transfer after submission |
| Exam records | Name, quantity, date: the record name, number of examinees, and assessment date of the same batch in the two materials must match | Check the required settings one by one, and confirm that submission is impossible when a required item is empty |
| Form input node | Required marking and field transfer: key material fields are marked as required, and subsequent nodes can obtain the corresponding field values after submission | Check the formInputResult field names in the node configuration, reference them in a subsequent node, and run a test |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the courseware and the handover record. Cause: Drafting and handover are filled in separately, without field-level verification.
- Symptom: The version is not synchronized, and old courseware and new procedures circulate at the same time. Cause: The form does not record the version number and revision date, and no comparison is made during handover.
- Symptom: Signatures or receipts are missing, and the material cannot be issued. Cause: The signature column and receipt column are not marked as required, and subsequent nodes cannot obtain values after submission.
How to verify the setup
Acceptance of this feature: fill it out once and submit, check the field values obtained by subsequent nodes, and confirm that the formInputResult and selectResult field values can be passed correctly.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the field names one by one in the node configuration, and confirm that key material fields are marked as required.
- Reference this field in a subsequent node and run a test, and confirm that the field transfer after submission is correct.