Aglet

Triage a form that loses its draft on validation

Validation should help users correct a draft, not make them recreate it. Start with the submitted values and response, then compare what returns in the form across fields, nested inputs, selections, and long text.

Establish what is happening

  1. Inventory the draft

    Record field names, values or safe representatives, order, selection state, nested rows, attachments or references, and the validation error. Redact sensitive content while preserving enough structure to reproduce loss.

  2. Capture the recovery path

    Submit invalid data, inspect response status and URL, refresh, navigate back, and retry where relevant. Note which values survive, which reset, and whether browser history gives a dependable alternative.

  3. Bound user consequence

    Describe time lost, duplicate entry, missed context, or inability to correct a specific field. Separate a value that was never accepted from a value the server received but the form failed to redisplay.

What to carry forward

Triage should state invalid field, preserved and lost values, response path, reproduction sequence, and user consequence. Escalate when substantial work disappears or no dependable recovery exists; otherwise record a scoped draft-retention gap. Capture safe representatives of every submitted field and the returned form, including nested rows, selections, long text, and the exact invalid field that triggered recovery.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow