Version 0.43.0

New features

Save a search you keep running

The slice of the catalog you check every morning no longer has to be rebuilt every morning. Saved, next to the filters on the catalog page, keeps the search you are looking at under a name and puts it one click away.

It keeps the whole search, not just the words: the query, every filter chip, the tree or list view, and the sort order. Opening one puts the page back exactly as you left it.

Saved searches are yours alone. Nobody else sees them, and two people can each keep a "My services" without treading on each other. Rename one, delete one, or update it to match what is on screen once you have tweaked the search it opened. That last option only appears when the page has actually moved on from what you saved.

Want to share a search instead of keeping it? That is what a collection is for.

Improvements

Filters and the search box are now the same thing

Click a filter and it appears in the search box as text. Take it off and the text goes with it. What the box shows is the whole search that ran, so a filter you built by clicking is also a worked example of the query language, ready to edit when you need an "or" that chips cannot express.

It reads the other way too. Type kind:service and Service ticks in the kind picker, because a filter you wrote by hand belongs on the control that owns it as much as one you clicked.

Filters now open in a dialog rather than pushing the results down the page, with a running count at the top so you can see what each choice leaves you. And if your organization defines a lot of fields, you pick the ones you want to filter by instead of scrolling past all of them.

Build a collection by clicking, not by typing a query

Collections are now put together with the same search you use everywhere else. Whether you are writing the query behind a dynamic collection or picking entities for a static one, Filters opens the catalog's filter dialog and every choice you make writes itself into the search.

Saved starts you from one of your saved searches, so a view you already worked out can become a collection the whole team can see.

The picker also understands the full query language now, so you can find what you are adding with the same expressions the catalog takes rather than typing names one at a time.