What this category's data looks like
This page addresses the enterprise new employee onboarding training scenario, and the materials come from three categories: onboarding training plans, course sign-in sheets, and job descriptions. The onboarding training plan provides the course name, training date, and responsible person fields; the course sign-in sheet provides the sign-in date, participants, and signed receipt fields; the job description provides the job title, department, and responsibility item fields. The materials are updated weekly; the training plan is finalized before the class starts, the sign-in sheet is collected on the same day after each course ends, and the job description is synchronized with job adjustments. When entering the workflow, the onboarding training plan serves as the source of the main node, the course sign-in sheet serves as the item-by-item basis for progress records, and the job description serves as the reference draft for job attribution and statistical criteria. The fields, dates, and signatures of the three types of materials must be aligned item by item in the progress table, and only then can the record count and statistical count enter the weekly or monthly report.
Configuration and implementation checks
This step is executed by the workflow node (user selection and branching), outputting the branch direction and interaction state records. The "Progress Table and Statistical Criteria Description" is continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters the interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Onboarding training plan | Whether the course name, training date, and responsible person are consistent between the plan and the sign-in sheet | Compare the dates and signatures in the plan and the sign-in sheet item by item, and use nodeId to locate the corresponding node |
| Course sign-in sheet | Whether the number of participants and the sign-in receipts are complete, and whether entries missing signatures or receipts are listed separately | Summarize the number of sign-in entries weekly, check whether the statistical criteria are written in the header, and mark exceptions separately |
| Job description | Whether the job title and department match between the progress table and the description | Check the title and department fields job by job, and record entries whose versions are not synchronized separately |
| Progress table and statistical criteria description | Whether the record count and statistical count match, and whether the criteria are written in the header | Use one week of records to check the total, and check whether the variables references and branch direction are consistent |
Three common errors
- Phenomenon: The name, quantity, and date of the same participant record do not match between the plan and the sign-in sheet. Cause: The two materials are maintained separately and are not checked item by item under the same criteria.
- Phenomenon: After the job description is updated, the progress table still uses the old job title. Cause: The versions are not synchronized, and material updates do not trigger a review of the progress table.
- Phenomenon: The sign-in sheet contains entries missing signatures or receipts, and they are included in the total during statistics. Cause: Exceptions are not listed separately, and the statistical criteria are not written in the header.
How to verify the setup
This function's acceptance: run through each option, check the branch direction and interaction state in the run records, and confirm that the node corresponding to nodeId is consistent with the results passed by variables.
Business test: use one week of records to check the total, see whether the criteria and exceptions are clearly written, and whether the record count and statistical count match.
- In the node, check the options and branch connections one by one, trigger once, and view the node status in the run records.
- In subsequent nodes, reference the selection result variable and run once to confirm that the branch direction is consistent with the interaction state records.