What this category's data looks like
Undergraduate program revision materials include three types: program plans, course syllabi, and credit structure tables. Sources are academic affairs system exports and departmental submissions. The update cadence advances by academic year and revision batch. Field characteristics center on names, quantities, dates, signatures, and receipts. Program plans carry the program direction and curriculum system; course syllabi correspond to individual course objectives and assessment methods; credit structure tables record credit distribution and study requirements. When the three types of materials enter the authorized access and external services workflow, their roles differ: the program plan serves as the primary record for the external entry point, course syllabi serve as supporting attachments, and the credit structure table serves as the basis for verification. When parents or superiors access, the visible scope is jointly determined by identity and material version; restricted identities can only see versions that have been published and have completed signatures.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Externally available entry points and authorization scope" is then completed by subsequent nodes continuing execution along the branches. When a node is triggered, the conversation enters an interaction state and records the workflow state. After the user completes a selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Program plan | Whether the name, date, and signature are consistent with the course syllabi and credit structure table | In the node, check the options and branch connections one by one, confirm that the external entry point for the program plan points to the published version, and check whether signatures and receipts are complete |
| Course syllabi | Whether the same course name, quantity, and date match across the two materials | Trigger a user selection node once, view the node status in the run record, and confirm that the course syllabus attachments are synchronized with the program plan version |
| Credit structure table | Whether the credit quantity, date, and signature match the program plan and course syllabi | Reference variables in subsequent nodes and run a trial once, confirming that the credit structure table fields are consistent with the program plan and course syllabi |
| User selection node | Whether options and branches correspond one-to-one, and whether the interaction state is recorded | Check nodeId and branch connections, trigger a selection once, and view whether the interaction state and selection result variable are passed to subsequent nodes |
Three common errors
- Symptom: The same course's name or quantity does not match across the two materials. Cause: The course syllabi and program plan were revised separately, versions were not synchronized, and fields were not compared item by item.
- Symptom: The external entry point displays an old version of the program plan. Cause: The authorization scope was not filtered by version, and published versions and draft versions are mixed in the same entry point.
- Symptom: Materials are missing signatures or receipts. Cause: The revision process was not closed-loop, the signature node was not triggered, receipts were not archived, and visitors see incomplete records.
How to verify the setup
Acceptance for this feature: run trials option by option, check the branch directions and interaction states in the run records, 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, see whether the visible scope matches the settings, confirm that unauthorized content is not visible, and that the external entry point points to the published version.
- In the node, check the options and branch connections one by one, confirm that each option corresponds to one branch, and check whether the
nodeIdandvariablesreferences are correct. - Trigger a user selection node once, view the node status and interaction state in the run record, confirm that the selection result variable has been passed to subsequent nodes, and run a trial once.