This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Good Morning,
We are working with our users on adding Start Centers with specific Chart result set portlets. These will be assigned to different security groups, in order to give different work areas an "At a glance" view of their workload.
When creating/editing the portlet, it seems that you can only use Public Queries (at least if you want multiple users to be able to use the portlet.) However, in the past we have had to place a SIGOPTION on public queries (http://www-01.ibm.com/support/docview.wss?uid=swg21516270) in order to prevent them from being created because our users would complain about too many saved public queries on the Current Query menu cluttering it and making it hard for them to find their own saved queries. Though users with the proper rights can still create Public queries, we discourage that to prevent user complaints.
At this point, I'm trying to find a way to either:
A) Hide queries made for these portlets from showing up on the Current Query menu
or
B) Somehow share the queries needed for these portlets without marking them Public.
Has anyone run into a similar situation? Does anyone have any suggestions?
Thanks,
Jorge H. Collado
Information Systems Administrator
Orange County Utilities
PLEASE NOTE: Florida has a very broad public records law (F. S. 119).
All e-mails to and from County Officials are kept as a public record.
Your e-mail communications, including your e-mail address may be
disclosed to the public and media at any time.
We have users prefix their public query name with a site code and then use conditional ui to only show queries that apply to their site. Otherwise, with 125 sites, it is a real challenge to manage the list. You could prefix these portlet queries with their own code that would hide them from all users but allow you to add them to the Start Center. It is a work around at best, but I have yet to see an elegant way to deal with it.
Ron
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Monday, January 12, 2015 9:05 AM
To: maximo@yahoogroups.com
Subject: [MAXIMO List] Result Set Portlets Without Using Public Queries
Good Morning,
We are working with our users on adding Start Centers with specific Chart result set portlets. These will be assigned to different security groups, in order to give different work areas an "At a glance" view of their workload.
When creating/editing the portlet, it seems that you can only use Public Queries (at least if you want multiple users to be able to use the portlet.) However, in the past we have had to place a SIGOPTION on public queries (http://www-01.ibm.com/support/docview.wss?uid=swg21516270) in order to prevent them from being created because our users would complain about too many saved public queries on the Current Query menu cluttering it and making it hard for them to find their own saved queries. Though users with the proper rights can still create Public queries, we discourage that to prevent user complaints.
At this point, I'm trying to find a way to either:
A) Hide queries made for these portlets from showing up on the Current Query menu
or
B) Somehow share the queries needed for these portlets without marking them Public.
Has anyone run into a similar situation? Does anyone have any suggestions?
Thanks,
Jorge H. Collado
Information Systems Administrator
Orange County Utilities
PLEASE NOTE: Florida has a very broad public records law (F. S. 119).
All e-mails to and from County Officials are kept as a public record.
Your e-mail communications, including your e-mail address may be
disclosed to the public and media at any time.
We recommended the users prefix them but not all follow the guidelines. We have an administrator who create one site level default start page for each site and they create the query and do not set it up as public, but they do associate it with the template. The results are displayed on the start center with all those that have the access to that template but have no access to the query itself and it does not appear on the query list because it is not public.
Roy Cline
Phone: (203) 492-8189
Cell: (203) 640-9743
FAX: (203) 492-8462
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com]
Sent: Monday, January 12, 2015 10:56 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] RE: Result Set Portlets Without Using Public Queries
We have users prefix their public query name with a site code and then use conditional ui to only show queries that apply to their site. Otherwise, with 125 sites, it is a real challenge to manage the list. You could prefix these portlet queries with their own code that would hide them from all users but allow you to add them to the Start Center. It is a work around at best, but I have yet to see an elegant way to deal with it.
Ron
From: MAXIMO@yahoogroups.com<mailto:MAXIMO@yahoogroups.com> [mailto:MAXIMO@yahoogroups.com]
Sent: Monday, January 12, 2015 9:05 AM
To: maximo@yahoogroups.com<mailto:maximo@yahoogroups.com>
Subject: [MAXIMO List] Result Set Portlets Without Using Public Queries
Good Morning,
We are working with our users on adding Start Centers with specific Chart result set portlets. These will be assigned to different security groups, in order to give different work areas an "At a glance" view of their workload.
When creating/editing the portlet, it seems that you can only use Public Queries (at least if you want multiple users to be able to use the portlet.) However, in the past we have had to place a SIGOPTION on public queries (http://www-01.ibm.com/support/docview.wss?uid=swg21516270) in order to prevent them from being created because our users would complain about too many saved public queries on the Current Query menu cluttering it and making it hard for them to find their own saved queries. Though users with the proper rights can still create Public queries, we discourage that to prevent user complaints.
At this point, I'm trying to find a way to either:
A) Hide queries made for these portlets from showing up on the Current Query menu
or
B) Somehow share the queries needed for these portlets without marking them Public.
Has anyone run into a similar situation? Does anyone have any suggestions?
Thanks,
Jorge H. Collado
Information Systems Administrator
Orange County Utilities
PLEASE NOTE: Florida has a very broad public records law (F. S. 119).
All e-mails to and from County Officials are kept as a public record.
Your e-mail communications, including your e-mail address may be
disclosed to the public and media at any time.
You can try going to the global restrictions option in security groups application, and creating a object level global restriction on queries. Create one of QUALIFIED type and make it applicable only to the application. i.e., if the queries are on SR, make the restriction applicable to SR app only. You can create a domain like QUERIESTOHIDE, and add the query IDs there, for easy maintenance. Then, code your QUALIFIED restriction to show only those queries whose name does NOT appear in QUERIESTOHIDE domain.
So, what will happen is that when in the SR app, these queries will not be accessible in the queries drop down. However, since the restriction is restricted to SR app, they should still be available for use in the start center result portlet.