What this category's data looks like
This category's data includes the program offerings filing form, talent demand justification, and faculty and equipment list. The filing form contains the program name, code, program length, enrollment number, signature, and date; the justification contains industry positions, demand quantity, and survey date; the list contains faculty names, titles, equipment names, quantities, and purchase dates. The materials come from academic affairs, secondary colleges, and the human resources department, are updated according to the academic-year application cycle, and the version is based on the signed receipt. When entering the workflow, the filing form serves as the main record, while the justification and list serve as supporting attachments, and the fields of the three must be cross-consistent. Workflow nodes read these materials so that subsequent nodes can generate external entry points and authorization scopes according to branches.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "External entry points and authorization scopes" are completed by subsequent nodes continuing execution according to the branches. When a node is triggered, the conversation enters an interaction 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 |
|---|---|---|
| Program offerings filing form | Whether the name, code, date, signature are consistent with the talent demand justification and the faculty and equipment list | Check the options and branch connections one by one in the node, access once with a restricted identity, and verify the visible scope and signed receipt |
| Talent demand justification | Whether the position names, demand quantity, and survey date match the filing form and the list | Reference variables in subsequent nodes and run a trial, and verify whether the justification fields are synchronized with the filing form |
| Faculty and equipment list | Whether faculty names, titles, equipment names, quantities, and purchase dates are consistent with the filing form | Check the node status corresponding to nodeId in the run records, and inspect differences between the list and the filing form |
| External entry points and authorization scopes | Whether the visitor identity matches the visible scope, and whether unauthorized access is invisible | Trigger an interaction once, and check the branch direction and interaction state in the run records |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the filing form and the faculty and equipment list. Cause: The two materials are filled in separately by different departments, no cross-check is performed, and versions are not synchronized.
- Symptom: The survey date of the talent demand justification differs greatly from the signature date of the filing form, and the signature or receipt is missing. Cause: When materials are updated by academic year, receipts are not unified, and old versions are still in circulation.
- 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 one by one, and the selection result variable was not correctly passed to subsequent nodes.
How to verify the setup
Feature acceptance: run trials for each option one by one, check the branch direction and interaction state in the run records, confirm that options correspond one-to-one with branches, 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 setting, and confirm that unauthorized content is invisible.
- Check the options and branch connections one by one in the node, reference
variables, and run a trial once. - Check the node status corresponding to
nodeIdin the run records, and confirm that the interaction state is recorded.