Build a useful investigation brief
Map field rules
Write the required, optional, format, default, and role-specific rule for every visible field. Compare labels and hints with server validation and error messages. Note whether an invalid value is rejected before submission or only after a response returns.
Trace persistence
Submit one field at a time in a synthetic fixture, then reload the profile and next page. Compare request values, saved values, and displayed values without using personal data. Check whether a partial save is intentional, rejected, or simply not surfaced to the person.
Follow resume paths
Skip optional details if supported, leave during validation, use back navigation, and return from workspace or project setup. Record route, heading, focus, and next action. Compare supported roles so an unavailable action is not misread as a broken form.
What to carry forward
The investigation is ready when form rules, response validation, saved values, redirect, and resume state are traceable for a reproducible synthetic profile. Deliver the first mismatch and distinguish copy, persistence, and authority hypotheses with evidence.
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