What this category's data looks like
This page focuses on exception tracing and manual review for enterprise compliance and safety training, involving three types of materials: compliance training courseware, safety operating procedures, and exam records. Courseware is usually updated quarterly or annually, with fields including course name, version number, release date, applicable position, and instructor signature; operating procedures are revised immediately as equipment or processes change, with fields including procedure number, effective date, revision record, and approval signature; exam records are generated per session, with fields including candidate name, exam paper version, score, invigilator signature, and receipt date. When the three types of materials enter the form input node, each plays a different role: courseware and procedures are used to check whether the name, quantity, and date of the same record are consistent, and exam records are used to check whether signatures and receipts are complete. The material sources are internal training systems or paper archives, the update cadence is driven separately by the compliance department and the safety department, and the field characteristics center on dates, versions, and signatures, making it easy for subsequent nodes or humans to trace back to the source accordingly.
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). The "exception list and review conclusion" is completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters an interactive state and the workflow state is recorded. 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 include course name, version number, release date, applicable position, and instructor signature; check whether the name and date are consistent with the exam records | Check the field names one by one in the node configuration, and confirm they correspond one-to-one with the courseware material fields |
| Safety operating procedures | Fields include procedure number, effective date, revision record, and approval signature; check whether the version is synchronized and whether the signatures are complete | Check the required settings one by one, and confirm that the procedure number and effective date are marked as required |
| Exam records | Fields include candidate name, exam paper version, score, invigilator signature, and receipt date; check whether the receipt date and signature are missing | Reference the formInputResult fields in subsequent nodes and run a trial to confirm that the corresponding field values can be retrieved |
| Form input node | After being triggered, the conversation enters an interactive state and the workflow state is recorded; after submission, the field values are passed to subsequent nodes | Use userSelect to select the reviewer, and run a trial to confirm that subsequent nodes can retrieve the values after submission |
Three common errors
- Symptom: The course name and date of the same record do not match between the courseware and the exam records. Cause: The two materials are maintained by different departments, their update cadences are not synchronized, and the name and date fields are not forcibly checked in the form.
- Symptom: The version of the safety operating procedure is not synchronized, and the old version of the procedure is still referenced. Cause: The revision record and effective date fields are not marked as required, there is no version comparison step at submission, and subsequent nodes retrieve the old version's field values.
- Symptom: The exam record is missing the invigilator signature or receipt date, and the review conclusion cannot be signed off. Cause: The signature and receipt fields are not set as required, subsequent nodes cannot retrieve the corresponding field values after submission, and manual review finds the materials incomplete.
How to verify the setup
Acceptance of this feature: fill out the form once and submit it, check whether the field values retrieved by subsequent nodes are consistent with the filled-in content, and confirm that formInput is passed correctly.
Business test: create an exception record, see whether the source material can be traced, and check whether the names, dates, and signatures of the courseware, procedures, and exam records match.
- Check the field names one by one in the node configuration, and confirm they correspond one-to-one with the fields of the compliance training courseware, safety operating procedures, and exam records.
- Check the required settings one by one, confirm that the key material fields are marked as required, and use
userSelectto select a reviewer and run a trial submission.