Forms and User Interaction for Exam Organization and Misconduct Handling: Manage Authorized Access and External Services

Exam Administration: review forms for authorized access. Compare the source records, required inputs and downstream results before handing the task over.

What this category's data looks like

Exam organization and violation handling involve three types of materials: exam manuals, exam room record sheets, and violation fact records. Exam manuals define procedures and authorization levels, exam room record sheets record on-site conditions, and violation fact records are used for determination and disposition. Materials are updated by the exam department per session, and manuals are revised per semester. Fields include candidate name, exam room number, violation date, fact description, invigilator signature, and receipt status. After entering the form input node, manual fields correspond to authorization scope and visible identity, exam room record sheet fields correspond to on-site data, and violation fact record fields correspond to fact determination. The field names, quantities, and dates of the three types of materials must be consistent, and signatures and receipts must not be missing.

Configuration and implementation checks

This step is executed by the form input node (interaction node) in the workflow, which outputs the field values filled in by the user (passed to subsequent nodes after submission). The externally available entry points and authorization scope are then completed by subsequent nodes or manually.

ObjectCheckVerification action
Exam manualWhether the authorization scope and visible identity are graded according to the manual, and whether the same record name, quantity, and date are consistent across the three materialsCheck field names one by one in the node configuration, and compare the corresponding items in the exam room record sheet and violation fact record
Exam room record sheetOn-site data fields correspond one-to-one with manual requirements, and the violation date matches the fact record dateCheck the required settings, and confirm that the invigilator signature and receipt status fields are marked as required
Violation fact recordFact determination fields are complete, and submission is not allowed when signature or receipt is missingReference the formInputResult and selectResult fields in subsequent nodes and run a test to confirm the corresponding values are obtained
Form input nodeAfter triggering, the conversation enters the interaction state and records the workflow state; after submission, the fields are passed to subsequent nodesFill in the required items once and submit, then check the field values obtained by subsequent nodes

Three common errors

  • Symptom: The name, quantity, and date of the same violation record do not match between the exam room record sheet and the violation fact record. Cause: The two materials are entered separately, and fields and versions are not unified according to the exam manual.
  • Symptom: The exam manual has been revised, but the exam room record sheet still uses old-version fields, and the authorization scope and visible identity do not match. Cause: The version was not synchronized, and the form fields were not updated with the manual.
  • Symptom: The violation fact record lacks an invigilator signature or receipt, but it still proceeds to subsequent nodes after submission. Cause: The required markers do not cover the signature and receipt fields, and the interaction state does not intercept it.

How to verify the setup

Acceptance for this feature: Fill in and submit once, check the field values obtained by subsequent nodes, confirm that both the formInputResult and selectResult fields can be referenced, and that the conversation does not get stuck in the interaction state.

Business test: Access once with a restricted identity, check whether the visible scope matches the settings, and ensure unauthorized content is not visible.

  • Check field names and required settings one by one in the node configuration, and ensure that key material fields are marked as required.
  • Reference the formInputResult and selectResult fields in subsequent nodes and run a test to confirm that the corresponding field values can be obtained after submission.