What this category's data looks like
The materials on this page come from the kindergarten operation behavior and quality self-assessment scenario, including three types of materials: self-assessment reports, issue lists, and rectification plans, as well as externally accessible entry points and authorization scope descriptions. Self-assessment reports are updated by semester or academic year, with fields covering operating conditions, safety and hygiene, care and education, faculty and staff, and internal management, including dates and signatures; issue lists are updated by occurrence, recording issue descriptions, responsible persons, rectification deadlines, and receipts; rectification plans are updated by round, recording measures, completion dates, and acceptance signatures. When these three types of materials enter workflow orchestration, the self-assessment report serves as the draft for external display and superior review, the issue list serves as the basis for internal verification and rectification tracking, and the rectification plan serves as the filtering object for the scope visible to parents or superiors. It is common for the same record name, quantity, and date to fail to match across materials, for versions not to be synchronized, and for signatures or receipts to be missing.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Externally accessible entry points and authorization scope" is then completed by subsequent nodes continuing execution according to the branch. When the user selection 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 |
|---|---|---|
| Self-assessment report | Whether the kindergarten name, number of classes, date, and signature in the report are consistent with the issue list and rectification plan | Check the options and branch connections one by one in the node, trigger one user selection, view the node status in the run record, and use variables and nodeId to locate the branch |
| Issue list | Whether the issue description, responsible person, rectification deadline, and receipt correspond item by item with the rectification plan, and whether the versions are synchronized | Reference the selection result variable in a subsequent node and run a trial once, checking the names, quantities, and dates of the list items against the plan items |
| Rectification plan | Whether the measures, completion date, and acceptance signature are complete, and whether they are consistent with the self-assessment report's standards | Access once with a restricted identity, see whether the visible scope matches the settings, and confirm that unauthorized content is not visible |
| Externally accessible entry points and authorization scope | Whether the visitor's identity matches the visible scope, and whether the content visible to parents or superiors contains only materials with signed receipts | Check the branch corresponding to each option in the node, and confirm that after a restricted identity enters, the branch direction is consistent with the interaction state record |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the self-assessment report and the issue list. Cause: The two materials are maintained separately, and field alignment and version synchronization were not performed before entering the workflow.
- Phenomenon: The rectification plan has been updated, but the external entry point still displays the old version. Cause: The version was not synchronized, the branch direction was not reselected according to the latest materials, and the interaction state record was not updated.
- Phenomenon: The issue list lacks a signature or receipt but is still included in the externally visible scope. Cause: The authorization scope judgment did not check the signature and receipt fields, resulting in unauthorized visibility when accessed with a restricted identity.
How to verify the setup
Acceptance of this feature: Run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and use variables and nodeId to locate.
Business test: Access once with a restricted identity, see whether the visible scope matches the settings, and confirm that unauthorized content is not visible.
- Check the options and branch connections one by one in the node, trigger one user selection, and view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once, checking the names, quantities, dates, and signature receipts of the self-assessment report, issue list, and rectification plan.