What you are seeing is the current OOTB behavior of Constellation Search and Select / Advanced Search, rather than a normal Screen Flow state-management issue.
The Reset action is designed to clear only the search-form inputs. It does not reliably clear the control’s retained results/selection state, and when the user navigates forward and then returns to the prior screen, the transient Advanced Search container can rehydrate with its earlier criteria/context.
The Advanced Search fields are not ordinary properties on the case page. Pega builds the Search and Select search form in a transient container, so its criteria do not participate in the primary case payload in the same way as top-level case properties. This is why navigation in a Screen Flow can produce unexpected retained state and why normal form-refresh patterns do not apply.
For a Screen Flow where the search criteria need to survive navigation and be reliably cleared, avoid using Advanced Search as the state holder. Instead-
- Create normal, top-level case properties such as: FirstName, LastName, DOB etc
- Put those properties on the first Screen Flow assignment/view.
- Use those properties as parameters to a parameterized data page or query/report definition that returns the matching records.
- Show the results in the next assignment or in a conditional region of the same assignment.
- Add an explicit Clear search action that sets the case-level search properties to blank, clears the selected data reference, and refreshes/hides the results region, based on whether minimum search fields are populated.
However, if you cant avoid Advanced Search, treat Reset as “clear criteria only,” not “return the whole control to its initial state". Show the ‘result’ region only when the required criteria is populated and once Reset clears them, the result section can be conditionally hidden.
Also, do not rely on Advanced Search inputs to drive downstream Screen Flow logic or persist data between steps, instead consider a custom DX component only if the UX must remain exactly like Advanced Search and the behaviour is a hard business requirement. This adds implementation and upgrade ownership, so it should be a last resort