It looks like it's a way to expose all saved queries in the REST API to that object structure in apps the user has access. For example, if your object structure was set to INTEGRATION instead of REPORTING and in the WOTRACK you had a public query of getMyWork, that saved query would be available automatically to that object structure if they had READ access to WOTRACK. If the user had READ access to PLUSPWO and there was a public query for getMyCustomerWork they would have access to that as well. Anything where your main object is the main object of the app and the user has access to it. This also would include private queries that they created.
You can see the queries available by making an API call like: /
maximo/api/apimeta/mxapiasset?lean=1
In general, I've seen the list manually managed by choosing the Query Definition action. This allows you to specify an OS specific where clause, an automation script, or a saved query from an app. But in the last scenario you would have to specify exactly which ones you wanted the user to be able to access and this flag would grant them access to all without having to add any.
Potentially a good reason for doing something like this is when you have an external UI of the Maximo application and want to surface these queries to your users automatically. As new saved queries get added they become immediately available to your object structure and thus your external application.
------------------------------
Steven Shull
------------------------------
Original Message:
Sent: Mon November 01, 2021 09:36 AM
From: User1971
Subject: Object Structure --> Load Query From All Apps
MAM 7.6.1.2:
What is the purpose of this field?
Object Structure --> Load Query From All Apps
I tried googling "maximo" "Load Query From All Apps" but didn't get any results.
Thanks.
#Maximo
#AssetandFacilitiesManagement