What this category's data looks like
In the student disciplinary action and appeal handling scenario, materials enter the form input function in batches by node, each taking on a different role. Disciplinary fact materials enter at the preliminary review stage, with fields including the name of the person reported, class, date the facts occurred, description of circumstances, source of materials, and handler's signature, used to fix the factual basis; the disciplinary decision enters at the deliberation stage, with fields including the name of the disciplinary action, the clauses relied upon, decision date, method of service, and receipt signature, used to form an externally effective text; the appeal statement enters at the relief stage, with fields including the appellant's identity, appeal request, factual grounds, submission date, and acknowledgment record, used to initiate review. The three types of materials update at different rhythms: fact materials are supplemented as the investigation progresses, the decision is finalized according to the deliberation conclusion, and the appeal statement is fixed at the point of submission. Field characteristics are concentrated in four categories: name, quantity, date, and signature. If the same record has inconsistent name, quantity, or date across two materials, or if versions are not synchronized, or signatures and receipts are missing, it will cause confusion in values retrieved at subsequent nodes.
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 point and authorization scope are then completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Disciplinary fact materials | Whether the name, quantity, date, and signature are consistent with the disciplinary decision | Check field names one by one in the form input node, and compare the name of the person reported, the quantity of circumstances, and the date the facts occurred in the two materials |
| Disciplinary decision | Whether the name of the disciplinary action, the clauses relied upon, the decision date, and the receipt signature are complete | Check the required markers, confirm that the decision date and service receipt signature fields have been filled in, and check whether the versions are synchronized |
| Appeal statement | Whether the appellant's identity, appeal request, submission date, and acknowledgment record correspond | Reference the field values obtained by formInput in subsequent nodes, and run a test to confirm that the appeal request and submission date can be passed correctly |
| External entry point and authorization scope | Whether the visitor's identity matches the visible scope, and whether unauthorized access is invisible | Use userSelect to specify a restricted identity for one access, and check whether the visible field scope matches the setting |
Three common errors
- Symptom: The name and quantity of the same record do not match between the disciplinary fact materials and the disciplinary decision. Cause: The fields in the two places are entered separately, without cross-comparison.
- Symptom: The version of the disciplinary decision is not synchronized, and subsequent nodes retrieve old field values. Cause: The version identifier and date are not checked after form submission.
- Symptom: The appeal statement lacks a signature or receipt, and the record is incomplete. Cause: The required markers do not cover the signature and receipt fields, so empty values can also be submitted.
How to verify the setup
This feature's acceptance: fill in once and submit, check the field values retrieved by subsequent nodes, and confirm that the fields corresponding to formInputResult and selectResult can be passed correctly.
Business test: access once with a restricted identity, and see whether the visible scope matches the setting.
- Check field names one by one in the node configuration, and confirm that they correspond one-to-one with the fields of the disciplinary fact materials, disciplinary decision, and appeal statement.
- Check the required settings one by one, and reference the field in a subsequent node for a test run, confirming that the value can be retrieved after submission.