Hi Shannon,
That's true - I've seen several approaches for a separate Maximo Application managing Queries. We did also develop such an application, but that would be a commercial product:
https://youtu.be/qYKhunpETaIIn general, the concept is:
- We make all Queries public
- Admins would have to associate a Query with a User Group for visibility
- If a Query should be really public - assign MXEVERYONE Group
- MAXADMIN or Users with appropriate permissions are allowed to modify queries they're NOT owner of as well. I believe, that includes delete
- The application does also provide some nice extra function like "Check Query" or "Go to Application"
Many Greetings from Switzerland,
------------------------------
Johann Rumpl
Maximo Senior Consultant
EAM Swiss GmbH
Gais
Switzerland
------------------------------
Original Message:
Sent: Mon July 05, 2021 05:49 PM
From: Shannon Rotz
Subject: Manage public queries/reports via a generic user?
Further to Stephen's post: I believe someone else has created a custom application that ties to the QUERY table, to allow IT users to change the Owners via the GUI. Note, however, that if you change the Owner of a query that is used on a Start Center Result Set, the Result Set won't display properly for the users. You need to update the template and re-create the Result Set, and then get the users to Update Start Center afterwards.
------------------------------
Shannon Rotz
InComm Solutions
New Westminster BC
Original Message:
Sent: Sun July 04, 2021 11:33 PM
From: User1971
Subject: Manage public queries/reports via a generic user?
My organization has come across a scenario where public queries and reports were created by user x, and now user x has left the organization.
It's my understanding, as an I.T. user with MAXADMIN security, that I won't be able to edit or delete queries/reports that were created by user x. I'm told that the only way to handle this scenario is to get our DBA to modify the underlying db records via an UPDATE statement...changing the owner to MAXADMIN...and then login as MAXADMIN to edit the queries/reports (which non-DBAs still can't do -- since we don't use the MAXADMIN user -- it's reserved for the DBA).
This situation isn't ideal. My organization needs a way for IT analysts (with MAXADMIN security) to be able to manage public queries and reports.
BMXAA3897E - Only the creator of this query can delete it.
Note: The current IT user does have MAXADMIN security, but still can't delete the query.
Questions:
1. Are the limitations mentioned above correct?
2. To avoid that scenario, should we only ever create public queries and reports by using a custom QUERYADMIN user?
- Multiple I.T. staff would use that user -- but only for managing public queries and reports.
- We'd remove the 'Public?' checkbox from the save query window for regular users -- via a security setting.
3. Or are there other options?
Thanks.
#Maximo
#AssetandFacilitiesManagement