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.
The solution is to enable customers to define lookup datasources that should not be included in the preload database. IE a flag on the maximo-datasource that says mobile-preload="false" to indicate that it should not be included in the preloaded database and downloaded interactively as the user (similar to transaction data). This would enable all Maximo data restrictions to be applied while still taking advantage of the preload database on the bulk datasets (asset, locations, inventory, etc.) that lead to performance challenges in the fields.
Customers cannot opt out of preload databases given their importance in performance. And it works well for the majority of the datasets. But there are a few that tend to be small datasets (most customers only allow users to report labor for themselves or their crew) that have high variability that would benefit being retrieved using the REST API instead.
Functionality is already available when user is not using Preloaded databases. While preload acts as a template for multiple users (regardless of security), the classic method of not using preloaded databases would use current user's credential to download the data, hence respecting the defined security privileges in base Maximo. There is not a technical way to support classic Maximo security settings - data restrictions (sql driven approach) to the Mobile app (qbe approach). Thanks for your feedback!