What this category's data looks like
This category's data looks like this: Social evaluation of vocational skill level certification involves materials such as the evaluation implementation plan, candidate registration form, and assessor dispatch form. The sources are the evaluation agency and the certification platform, and the update rhythm rolls forward with policy adjustments, batch changes, and personnel movements. The evaluation implementation plan contains the evaluation occupation, level, time, location, evaluation method, and signature field; the candidate registration form contains name, ID number, declared occupation, level, date, and receipt; the assessor dispatch form contains the assessor's name, certificate number, dispatch date, and signature. When the materials enter workflow orchestration, the implementation plan serves as the main workflow trunk, while the registration form and dispatch form serve as branch bases and verification objects, each taking on the role of field checking and version traceability.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Evaluation implementation plan | Whether the fields, dates, and signatures match the registration form and dispatch form | Check the occupation, level, time, location, and signature field one by one, reference nodeId to locate the node, and run a trial to see the branch direction |
| Candidate registration form | Whether the name, ID number, declared occupation, level, date, and receipt are consistent | Reference variables in subsequent nodes to obtain the selection result variable, and compare the dates and signatures of the registration form and implementation plan item by item |
| Assessor dispatch form | Whether the assessor's name, certificate number, dispatch date, and signature are consistent with the implementation plan | Trigger a user selection node once, check the node status in the run record, and verify the names and dates in the dispatch form and implementation plan |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, run a trial to check whether the version number and references are updated synchronously, and record the interaction status |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the implementation plan and the registration form. Cause: The two materials are maintained separately, and fields and signatures are not uniformly checked after the user selection node.
- Symptom: The version is not synchronized, and the old version is still referenced. Cause: After the change, the user selection node was not triggered to go through the branch again, and subsequent nodes still continue execution according to the old variables.
- Symptom: A signature or receipt is missing, and the process stops after the interaction is completed. Cause: The material did not return the signature page, the user selection node did not record the complete interaction status, and the branch cannot continue.
How to verify the setup
How to verify the setup: Acceptance of this feature: run trials for each option one by one, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and verify by referencing variables and nodeId.
Business test: change one piece of content, see whether the version number and references are updated synchronously, and check whether the fields, dates, and signatures of the evaluation implementation plan, candidate registration form, and assessor dispatch form are consistent.
- In the user selection node, check the options and branch connections one by one, run a trial once, and view the node status in the run record.
- Reference the selection result variable in subsequent nodes and run a trial to check whether the version ledger and change records continue execution according to the branch.