What this category's data looks like
In the enterprise self-directed skilled-talent evaluation scenario, the category materials entering the intake stage are mainly of three types: the enterprise evaluation filing form, the evaluation specification, and the candidate roster. The filing form comes from enterprise declaration and the competent department's receipt, is updated by batch, and its fields include unit name, occupation name, level, evaluation date, and signature and seal positions; the evaluation specification comes from enterprise technical documents and question-bank descriptions, is re-versioned as standards are revised, and its fields include occupation direction, assessment modules, weights, version number, and effective date; the roster comes from registration summaries, is updated on a rolling basis by batch, and its fields include name, ID number, declared level, trade, and unit. After the three types of materials enter the workflow of question-and-answer intake and missing-item follow-up, the filing form is used to determine whether the declaring entity and batch are valid, the evaluation specification is used to determine whether the assessment items and basis are complete, and the roster is used to determine whether the individual candidate information corresponds to the declaration conditions. When material versions, dates, and signature positions are inconsistent, the intake side must first identify the missing items and follow up, then transfer to the handler.
Configuration and implementation checks
This link is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "Intake records and the questions to be completed" are continued and completed by subsequent nodes according to the branches. 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 |
|---|---|---|
| User selection node | Each option corresponds to one branch; options and branch connections must be matched one by one | Check options and branch connections one by one in the node, and confirm that the selection result variable has been passed to subsequent nodes |
| Enterprise evaluation filing form | Whether unit name, occupation name, level, evaluation date, and signature position are consistent between the filing form and the receipt | Compare the two materials field by field, and mark records where names, quantities, or dates do not match or signatures are missing |
| Evaluation specification | Whether the version number, effective date, and assessment modules are consistent with the current batch | Check entries whose versions have not been synchronized, and confirm that the referenced content corresponds to the effective version |
| Candidate roster | Whether name, ID number, declared level, and trade correspond between the roster and the filing form | Compare the fields of the same record in the two materials one by one, record inconsistent items, and follow up |
Three common errors
- Phenomenon: the name, quantity, and date of the same record do not match between the filing form and the roster. Cause: the two materials are filled in at different stages, and intake proceeds without field-level comparison.
- Phenomenon: the evaluation specification version has not been synchronized, and old assessment modules are still referenced. Cause: after re-versioning, the effective date and version number were not checked, and the referenced content is out of step with the current batch.
- Phenomenon: the filing form lacks a signature or the receipt is missing, yet intake continues. Cause: signature positions and receipts are not treated as pre-intake check items, and missing items are not identified and followed up.
How to verify the setup
Feature acceptance: run trials option by option, check the branch directions and interaction states in the run records, and confirm that the selection result variable has been referenced in subsequent nodes.
Business test: submit a question missing key information, and see whether it follows up first before answering.
- Check options and branch connections one by one in the node, confirming that each option corresponds to one branch and that no default branch is taken by mistake.
- Reference the selection result variable in a subsequent node and run a trial once, checking the values of
variablesandnodeIdin the run records.