What this category's data looks like
This page focuses on authorized access and external services for social evaluation of vocational skill level certification. The materials come from the evaluation implementation plan, candidate registration forms, and assessor dispatch forms. The evaluation implementation plan determines the scope of certification and the level of authorization, the candidate registration form carries identity information and registration batch, and the assessor dispatch form records the dispatch date and signature. The three types of materials are updated by batch, and the fields include name, quantity, date, signature, and receipt. When the materials enter workflow orchestration, the evaluation implementation plan serves as the basis for the authorization scope, and the candidate registration form and assessor dispatch form serve as the basis for determining visitor identity and visibility scope. The update rhythm follows each certification batch as the cycle, and the field characteristics require that the same record be consistent across materials in name, quantity, and date, with complete signatures and receipts.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Externally available entry points and authorization scope" are then completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Evaluation implementation plan | Whether the authorization scope and certification level cover the external service targets, and whether the name, quantity, date, and signature are complete | Check item by item the authorization level and external entry scope in the plan, compare the name, quantity, date, and signature, and use variables to record discrepancies |
| Candidate registration form | Whether the visitor identity and visibility scope match, and whether the name, quantity, and date of the same record are consistent between the plan and the registration form | Compare item by item the name, quantity, and date in the registration form and the plan according to restricted identity, check the signature and receipt, and use nodeId to locate the branch node |
| Assessor dispatch form | Whether the dispatch date and signature are complete, and whether the version is synchronized with the plan | Check the dispatch form date, signature, and receipt, inspect version synchronization, and reference variables in a subsequent node for a trial run |
| User selection node | Whether each option corresponds to one branch, whether the interaction status is recorded, and whether the selection result variable is passed to subsequent nodes | Trigger the node once, view the node status and branch direction in the run record, and reference variables in a subsequent node and perform a trial run |
Three common errors
- Symptom: The name, quantity, and date of the same candidate do not match between the registration form and the plan. Cause: The materials are maintained separately without cross-checking, resulting in deviation in determining the authorization scope.
- Symptom: The version of the assessor dispatch form is not synchronized, and the signature or receipt is missing. Cause: The update rhythm is inconsistent, and external services are still entered when the receipt is missing.
- Symptom: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked item by item, and the selection result variable was not passed correctly.
How to verify the setup
Acceptance of this function: run trial runs 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, and use nodeId to locate the node and variables to check whether the selection result variable is passed to subsequent nodes.
Business test: access once with a restricted identity, see whether the visibility scope matches the setting, and confirm that unauthorized content is not visible.
- In the node, check the options and branch connections one by one, and trigger once to view the node status in the run record.
- Reference the selection result variable in a subsequent node and perform a trial run once to confirm that the branch direction is consistent with the interaction status record.