What this category's data looks like
Graduate training process management involves materials such as training plans, proposal reports, and mid-term assessment forms. These come from supervisors, school secretaries, and the academic affairs system, and are updated according to semesters and training stages. The training plan includes course direction, credit requirements, and dates; the proposal report includes the title, review comments, and signatures; the mid-term assessment form includes progress, number of achievements, and supervisor comments. When these materials enter the authorized access and external services function, each has a different role: the training plan serves as the basis for the foundational scope, while the proposal report and mid-term assessment form serve as stage credentials, jointly determining the visitor's identity and visible scope. External services must match visible content according to visitor identity; unauthorized content must not be visible, and restricted access must be opened to parents or higher-level authorities. Material fields, dates, and signatures must be checked item by item to avoid the same record having inconsistent names, quantities, or dates across two materials, or versions not being synchronized, or missing signatures or receipts.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. "Externally available entry points and authorization scope" 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 |
|---|---|---|
| Training plan | Course direction, credit requirements, and dates must be consistent with the proposal report and mid-term assessment form | Check the name, quantity, and date of the same record in the two materials; check whether the versions are synchronized; confirm that signatures or receipts are complete |
| Proposal report | The title, review comments, and signatures must correspond to the mid-term assessment form and training plan | Compare dates and signature fields; view the branch direction and interaction status in the node run record corresponding to nodeId |
| Mid-term assessment form | Progress, number of achievements, and supervisor comments must match the training plan and proposal report | Check for missing signatures or receipts; reference variables in subsequent nodes and run a trial to confirm that the selection result variable has been passed |
| External entry points and authorization scope | Visitor identity matches the visible scope; unauthorized content is not visible | Access once with a restricted identity and see whether the visible scope matches the settings; check the variables and nodeId records |
Three common errors
- Symptom: The name, quantity, or date of the same record is inconsistent across two materials. Cause: The training plan and mid-term assessment form are entered separately, without field comparison and synchronization.
- Symptom: Versions are not synchronized, and an old proposal report is still referenced. Cause: After the material was updated, re-verification was not triggered, and the branch still follows the default path.
- Symptom: Signatures or receipts are missing, but the external entry point is still visible. Cause: The authorization scope was not narrowed according to signature status, and unauthorized visibility was not intercepted.
How to verify the setup
This feature acceptance: run trials option by option, and check the branch direction and interaction status in the run records; confirm that the node status corresponding to nodeId is recorded and that variables have been passed to subsequent nodes.
Business test: access once with a restricted identity and see whether the visible scope matches the settings; unauthorized content is not visible, and the scope opened to parents or higher-level authorities is correct.
- In the node, check the options and branch connections one by one, trigger once, and view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that the branch direction is consistent with the recorded interaction status.