Build a useful investigation brief
Build the transition table
Start with a query, filters, sort, and page, then record URL, request parameters, form values, results, and focus after each action. Include a result link and a copied URL. Keep one field that should reset as a deliberate control.
Find the first mismatch
Compare generated links, redirect parameters, form defaults, and server parsing. Check whether a missing value is dropped by a producer or ignored by the destination. Record a state that survives so the investigation does not overgeneralize from one action.
Write the contract brief
State persistence and reset rules by transition, the first failing boundary, and the smallest repair. Include narrow-layout behavior and an observable pass condition. Avoid attributing the loss to the browser when the URL itself no longer carries the field.
What to carry forward
The investigation is complete when each relevant transition has a reproducible state comparison and the first mismatch is named. Stop with a URL or rendering contract and one pass condition. If product intent is unsettled, separate that decision from the technical loss.
Technical background: Adobe developer documentation.
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