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

Possibility to modify "Quick Query"

Possibility to modify "Quick Query"

Within an Integrity Installation the "Quick Query" can't be modified.

For this installation you are limited to use existing -hard-coded- query definition,

 

My idea is the following:

  • Server-sided definition which will be used for each new account
  • Server-sided definition change can be distributed to all user which are using the unchanged last definition
  • Info to all user which have changed their "Quick Query", showing new server-sided definition (to take over if they want.)
9 Comments
Amethyst

Thank you for submitting this idea. We value your feedback however PTC Integrity R&D is not considering implementing this in future release of Integrity.

For this requirement you can always create a new query that suits your requirement instead of using a quick query.

Aquamarine

I disagree with decision for following reason:

Hard-coded  "Quick Query"  -like today- have the effect, that ...

EITHER  a customer needs to use the definitions included  FOR EVER  which causes to use certain field in every future Type (very bad idea !!).
             Follow-up effect:  Quick Query can't be used any longer as a simple "My items" view.

OR  We as customer need to bring e change to that query to every user. 

             (Will PTC pay us for this unnecessary effort?)

Judging over such an idea please always keep in mind that you speak with a customer that is representing thousands of user.

For me as a single I already have modified my Quick Query. My intention is to make life easier for each of my 50 new user per quarter.

Amethyst

I totally agree. It's a very, very simple fix that PTC could do that would make a big difference!

Amethyst

Theoretically the intention of quick query is only be used by you (user). It was not considered to be provided for any other purposes. Will it be feasible for to confirm why can't you use a named query for fulfilling your requirement?

Aquamarine

My idea does not discuss what is might be intended by any PTC Developer why he has created a hard-coded intial Quick Query which can be changed in any server settings. I understand that it is not intended as first query to show all items assigned to me, but you have to understand that it can be used that way.

And now each user starting with quick query will see his first assigned items  ...  thus he gets idea that this shows "his" items.

And for around 4000 user with up to 50 each month we are not able to tell of them that this is only an initial query available for every user.

For that reason I ask for a possibility to change today's hard-coded query definition.

Amethyst

The fact that it is intended to be used only by a user has nothing to do with the query's definition, that is not in question.

What is in question is the ability to pre-define the query for the user before instantiation. In other words, we want the ability to pre-define the quick query in a meaningful way.

I would add this side note: by default, a new user's query filter is always set to "that are my favorites". But as a new user, he/she has no favorites, so the list of queries is always empty. I'd like the ability to pre-define that filter or eliminate it.

Amethyst

Well, I think we are not trying addressing this problem here right? You are mixing it. We know the behaviour of "that are my favourites" for a new user brings nothing and we are thinking to change this in future release.

Aquamarine

Discussion is now really moving away from my initial idea.

I like to set a server-side definition for Quick Query, varying from today's hard-coded version + possibility to inform user about any change.

But I agree with idea of Laurent to remove default Quick Query to avoid occuring misunderstandings, if PTC does not like to open it for customer-specific definition.

Amethyst

Sorry for the confusion, I didn't mean to mix anything which is why I called it a side note.

I agree with the idea of a server-side admin-controlled pre-definition of the Quick Query.