What this category's data looks like
This category's data looks like this: For exception tracing and manual review of enterprise new employee onboarding training, the materials are concentrated in three types: onboarding training plans, course sign-in sheets, and job descriptions. Onboarding training plans are updated by batch, with fields including training name, course date, and responsible person's signature; course sign-in sheets are generated by session, with fields including trainee name, sign-in date, and sign-in handwriting; job descriptions are revised as positions are adjusted, with fields including position name, responsibility items, version number, and receipt signature. When these three types of materials enter the forms and interaction function, the onboarding training plan serves as the baseline for exception comparison, the course sign-in sheet serves as the original attendance record, and the job description serves as the basis for position attribution. The finished exception list and review conclusions are handled accordingly by subsequent nodes or manually, and handed over to the responsible person for disposition. In terms of field characteristics, names, quantities, dates, version numbers, and signature fields are the keys to tracing; the absence of any one of them will prevent the exception from being closed.
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 conclusions" are then completed by subsequent nodes or manually. 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 |
|---|---|---|
| Onboarding training plan | Training name, course date, and responsible person's signature match the course sign-in sheet item by item | Compare the training name, date, and signature fields of the two materials one by one, and record discrepancies in the exception list |
| Course sign-in sheet | Trainee name, sign-in date, and sign-in handwriting can correspond to the position attribution in the job description | Check the sign-in records against the position name and version number, and mark those missing signatures or receipts separately |
| Job description | Position name, responsibility items, and version number are synchronized with the version referenced by the training plan | Check the version number and receipt signature, and write those with unsynchronized versions into the exception list |
| formInput fields | Field names correspond one-to-one with material fields, and required markers cover key fields | Check field names and required settings one by one in the node configuration, and after submission check whether subsequent nodes can retrieve the corresponding field values |
Three common errors
- Phenomenon: The same trainee name is written differently in the sign-in sheet and the training plan, so it cannot be matched during tracing. Cause: The two materials are entered separately, without name and date comparison.
- Phenomenon: The job description has been revised, but the training plan still references the old version number, so the basis for the review conclusion is misaligned. Cause: The versions are not synchronized, and the update cadence is inconsistent.
- Phenomenon: The sign-in sheet lacks a signature or receipt, so the exception record cannot be attributed to the responsible person. Cause: Key fields are not marked as required, and after submission subsequent nodes cannot retrieve the values.
How to verify the setup
Acceptance of this function: fill out the form once and submit it, check whether the field values retrieved by subsequent nodes are consistent with what was filled in, and use formInputResult and selectResult for a trial run of referenced fields.
Business test: create an exception record, see whether it can be traced back to the source material, and confirm that the exception is supported by original records and the reviewer's signature.
- Check field names and required markers one by one in the node configuration, and confirm that key material fields are marked as required.
- Reference the
formInputResultandselectResultfields in subsequent nodes and run a trial, confirming that the corresponding field values can be retrieved after submission.