This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Internet of Things
Product family - Asset Management
Product - Maximo Asset Management (MAM)
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Asset Management
Product - Maximo Asset Management (MAM)
While I see Jason Verly's point on wanting a built-in / OOTB means of restricting the visibility of Saved Queries, I disagree with the idea of changing the QUERY object's Level to SITE. It doesn't make sense for the SR or Classification apps, for instance. As such restrictions would tend to be implementation-specific (e.g. why restrict on site? why not on a more granular custom field?), and as what he has asked for he should be able to do without customization through the configuration options available in Maximo (app designer, data restrictions, etc), I think the Query object should be left alone.