cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Allow a filter created using filtering in the Client to be saved as a query

Allow a filter created using filtering in the Client to be saved as a query

I frequently use the filtering in the client - using "where" - to query content items in documents, changes requests, defects, etc.  It would be very convenient if after defining the query in the client, I was able to have the ability to create a query using the specifications from the where filter.  This would be especially helpful if you are new to Integrity.  It would allow you to create a base query and then modify it as necessary.  For instance, when I began creating queries, I didn't understand the "Is content node" concept.  If I was able to create a query from the client filtering, it would have made query creation more intuitive.

@

2 Comments
Contributor

I can understand the difficulty in creating queries for new users, but the filter criteria cannot be used to define queries. Filtering and querying are for 2 different reasons and 2 different features, even though they may appear to be doing the same thing by helping user get to the correct information.

Contributor

It's possible in the WebUI: Save filters as new query.

So it can't be that hard to bring it to the client application, can it?