What this category's data looks like
This page's material comes from the daily records of kindergarten safety protection and emergency drills, including four categories: hazard items and rectification deadlines, drill participant counts and sign-ins, access control and school bus check items, and responsible person signatures. Hazard material is summarized weekly, drill material is archived per session, access control and school bus checks are filled in daily, and signature material is generated along with process nodes. After the material enters workflow orchestration, hazard items and rectification deadlines correspond to the hazard ledger, drill participant counts and sign-ins correspond to drill records, access control and school bus check items correspond to daily inspections, and responsible person signatures correspond to approval traces. In terms of update rhythm, hazards and check items change frequently, while drills and signatures are relatively stable. Field characteristics are mainly time, location, responsible person, and status, making it easy to trim the visible scope by identity in authorized access and external services.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Externally available entry points and authorization scope" is then completed by subsequent nodes continuing execution according to the branch. After the user completes the selection, the process continues execution along the branch corresponding to the selected option, and the finished product is then produced by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Hazard items and rectification deadlines | Whether the hazard is closed-loop and whether the rectification deadline is overdue | In the node, check the options and branch connections one by one, confirm that when the hazard is not closed-loop it goes to the not-closed-loop branch, and check the correspondence between nodeId and variables |
| Drill participant counts and sign-ins | Whether the drill record is consistent with the plan and whether the sign-in count matches | Trigger once, view the node status in the run record, check whether the participant count matches the plan, and confirm that variables has been passed to subsequent nodes |
| Access control and school bus check items | Whether check items are missing and whether responsible person signatures are complete | Reference variables in subsequent nodes and run a trial, confirm that when items are missing it goes to the supplementary inspection branch, and check that nodeId points correctly |
| Responsible person signatures | Whether signatures cover all check items and rectification items | Check the signature material and branch direction, confirm that when signatures are missing it goes to the supplementary signing branch, and record the interaction status corresponding to nodeId |
Three common errors
- Phenomenon: the hazard record shows rectification completed, but the deadline has passed and it is still not closed-loop. Cause: the options and branch connections do not cover the not-closed-loop case, and the process directly goes to the default branch.
- Phenomenon: the drill sign-in count is inconsistent with the plan count, but the record is still archived according to the plan. Cause: the interaction status was not recorded, and subsequent nodes cannot branch according to the actual count.
- Phenomenon: access control and school bus check items are missing, but signatures still show as complete. Cause: the selection result variable was not passed to subsequent nodes, and the supplementary inspection branch was not triggered.
How to verify the setup
This feature's acceptance: run trials for each option one by one, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, and that the selection result variable has been passed to subsequent nodes, and can be checked by referencing variables and nodeId.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and unauthorized content is not visible.
- In the node, check the options and branch connections one by one, and confirm that each option corresponds to one branch.
- Trigger the user selection node once, and view the node status and selection result variable in the run record.