You could work with an entity to store the search criteria. Create a 1-1 association with the user, so it will keep the previous settings even when you log out. (when a user logs in or goes to the home page, make sure to check if the associated object exists, otherwise create it)
This Search object should be the main parameter for your home page (in a dataview). Within the dataview you will add the Status field and you can add a list view (or you can look at other options to display lists) that fetches the applications based on an xpath. The xpath should be something like [Status = $SearchObject/Status]. Where SearchObject is the page parameter.
When you switch the Search status in you 1) save the SearchObject (because then it will be perstent for the next session as well) and you refresh the client. This will then either display the Active or Retired applications based on your selection. Search features of the ListView will continue to work within the context of the xpath.
Hope this helps.
Example of the domain model. The application and the search entity use the same status enum. You need an association to account or user to rertieve/create the personal search entity.
When you navigate to the search page, you will have to make sure there is a search object. This can be achieved via a microflow
The SearchEntity page has a dataview for your searchentity object and the list view for applications is using the SearchEntity status value to filter
With the following result