What this category's data looks like
This category's data involves three types of materials: course filing forms, study certificates, and credit recognition forms. Course filing forms are submitted by the educational institution, with fields including course name, number of class hours, course start date, and signature of the person in charge; study certificates are issued by the teaching provider, with fields including learner name, course name, completion date, and seal; credit recognition forms are compiled by the recognizing unit, with fields including recognized credits, recognition date, and reviewer signature. The material sources are dispersed across the institution, the teaching provider, and the recognizing unit, and the update pace advances with training batches, with multiple revisions possible within the same batch. When entering the authorized access and external services function, the course filing form serves as the basis for the scope that can be opened externally, the study certificate serves as the credential for matching visitor identity, and the credit recognition form serves as the result record for external output; the fields of the three must be aligned item by item to determine the visible scope.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "The externally available entry points and authorization scope" are then completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interactive 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 |
|---|---|---|
| Course filing form | Course name, number of class hours, course start date, and signature of the person in charge must be consistent item by item between the filing form and the study certificate | Check the name, quantity, date, and signature in the two materials, confirm there are no missing items, then reference variables to pass parameters |
| Study certificate | Learner name, course name, completion date, and seal must match the records in the filing form | Access once with a restricted identity, and view the branch direction and visible scope corresponding to nodeId in the run record |
| Credit recognition form | Recognized credits, recognition date, and reviewer signature must correspond to the completion records in the study certificate | Trial run each option, and check the branch results after variables is referenced in subsequent nodes |
| Authorization scope record | Visitor identity matches the visible scope, and unauthorized content is not visible | Trigger one interaction, and view the node status and selection result variables in the run record |
Three common errors
- Symptom: The course name, number of class hours, and date of the same record do not match between the course filing form and the study certificate. Cause: The two materials are filled out separately by the institution and the teaching provider, and the process proceeds without item-by-item comparison.
- Symptom: The credit recognition form has been updated, but the study certificate is still the old version, causing the visible scope to be inconsistent with the recognition result. Cause: The versions were not synchronized, and the fields were not rechecked after the materials were revised.
- Symptom: The course filing form lacks the signature of the person in charge, and the study certificate lacks a receipt, so the authorization basis cannot be confirmed during external services. Cause: The signature and receipt steps were not included in the material verification checklist.
How to verify the setup
Acceptance of this function: Trial run each option one by one, check the branch direction and interaction state in the run record, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
Business test: Access once with a restricted identity, and see whether the visible scope matches the setting and whether 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 trial run once to confirm that the process continues downward after the interaction is completed.